3 Answers
- Newest
- Most votes
- Most comments
0
Ok, thanks for confirming, AWS. I know when AWS says nothing, that means the bug is there, and they are working to fix it. 👍
answered 2 months ago
0
Can someone from the AWS CodeBuild service team please look into this.
I can reproduce this bug consistently.
Here's a repro case:
- Setup a GitHub Actions workflow that triggers two jobs at the same time via a matrix
- Use CodeBuild-based runners
- Trigger a run by pushing or whatever
What happens then:
- One of the job gets picked up and runs
- The second job gets stuck "Waiting for a runner to pick up this job... " and it never completes
- CodeBuild UI meanwhile shows no running jobs
My hunch is that there's a queue that receives these webhook events, and it probably deduplicates the events by something like a project name, or some run ID, that is not supposed to be unique.
answered a month ago
0
I think I found the issue.
In the Webhook request history in GitHub I see:
{"message":"Cannot have more than 1 builds in queue for the account"}
Which is really weird, provided that I did not make any changes on my account, and I have had > 2 running jobs in parallel before.
And all of the quotas are set to 15.
answered a month ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago