Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

concurrency github action run is causing failure #250

Open
lianhao opened this issue Nov 30, 2022 · 0 comments
Open

concurrency github action run is causing failure #250

lianhao opened this issue Nov 30, 2022 · 0 comments

Comments

@lianhao
Copy link
Contributor

lianhao commented Nov 30, 2022

Our current github action will cause failure when multiple runs are triggered in parallel. E.g. when jobs run in the following sequence, error happens:

  1. PR fix: hotelReservation README file subheading typo #242 triggered hotelReservation workflow run 3577351936
  2. PR HotelReservation: multiple bug fixings and enhancement #247 triggeredhotelReservation workflow run 3577352616.
  3. Run 3577351936 finished the job 'Calculate new version' and got the result of new version hotelReservation-0.0.2.
  4. Run 3577352616 finished the job 'Calculate new version' and got the result of new version hotelReservation-0.0.2.
  5. Run 3577351936 finished the job 'Create tag' and created a new tag hotelReservation-0.0.2.
  6. Job 'Create tag' of run 3577352616 failed, because the tag hotelReservation-0.0.2 it wanted to create was already existing. See https://github.com/delimitrou/DeathStarBench/actions/runs/3577352616/jobs/6016248939.
lianhao added a commit to lianhao/DeathStarBench-Upstream that referenced this issue Nov 30, 2022
Add concurrency control to avoid tagging failure when multiple parallel runs.

Fixed issue delimitrou#250.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant