-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
The job running on agent NetCore-Public ran longer than the maximum time #104044
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
I don't think we can excuse timeouts like this as a "Known Build Issue" because it could excuse a hang in the build itself. @dotnet/runtime-infrastructure I will close this issue. When opening these in the future they need to be more specific about a particular failing test or build step and the pattern needs to scope to that. For issues with slow machines, or delays in allocating machines, we unfortunately cannot use "Known Build Issues" to excuse them. |
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=720308
Build error leg or test failing: Build / linux-x64 Debug NativeAOT
Pull request: #103993
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=720308
Error message validated:
[The job running on agent NetCore-Public \d+ ran longer than the maximum time of \d+ minutes
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/26/2024 3:34:47 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: