On Sat, Mar 1, 2025 at 2:36 PM Paolo Bonzini <pbonz...@redhat.com> wrote: > > On 3/1/25 07:19, Stefan Hajnoczi wrote: > > Hi, > > On February 26th GitLab CI started failing many jobs because they > > could not be scheduled. I've been unable to merge pull requests > > because the CI is not working. > > > > Here is an example failed job: > > https://gitlab.com/qemu-project/qemu/-/jobs/9281757413 > > Hi Stefan, > > until February 26th the Digital Ocean runners were not enabled; I tried > enabling them (which is what caused the issue) to start gauging how much > credit we would need to be able to move from Azure to DO for CI. I > posted a note on IRC, I'm sorry if you missed that.
There is a new type of timeout failure: https://gitlab.com/qemu-project/qemu/-/jobs/9288349332 GitLab says: "There has been a timeout failure or the job got stuck. Check your timeout limits or try again" Duration: 77 minutes 13 seconds Timeout: 1h (from project) It ran 17 minutes longer than the job timeout. Any idea? Stefan
