-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
NativeAOT legs timing out in CI #102239
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
Clicking through, the problem is always the same - we finish product build in 20 minutes and send 5 workitems to helix (each of which takes less than a minute to run). We then wait for 100 minutes for these to finish. Then we timeout. Then 2 more hours later, the Helix workitems get finally scheduled and finish. Digging into Helix logs, it always looks something like this:
We could increase the timeout to 5 hours but that feels excessive. |
@markwilkie Could you comment on what "Delay" means here? Is there something holding up the run? |
@chcosta - any thoughts as to what 'Delay' means here?
|
looking |
I haven't had much time to dig into this yet |
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=675463
Build error leg or test failing: Build / linux-x64 Debug NativeAOT
Pull request: #102176
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=675463
Error message validated:
[ran longer than the maximum time of 120 minutes
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 5/15/2024 3:00:04 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: