-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Infra improvements for Helix #68176
Comments
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsList of requests from Helix to reduce failure overhead from PayloadGroup0, which seems to be returning a non-zero exit code very often.
|
Updated the 1600 -> 100 (the 1600 was from a bad query I made). 100 is still a lot per day though. |
I'm just following along for now; please ping me if you want me to participate in any investigations or check whether improvements work (though if the work items start passing, that's a very good sign) |
Tagging subscribers to this area: @hoyosjs Issue DetailsList of requests from Helix to reduce failure overhead from PayloadGroup0, which seems to be returning a non-zero exit code very often.
Runfo Tracking Issue: payloadgroup0 work item
Build Result Summary
|
@agocke Is it a good idea to have a tracking issue of such a wide issue with runfo? (aka, if the common coreclr tests fails fails, immediately add it here) |
I think this is no longer interesting -- we're tracking things at a more granular level now and this is just catching everything in coreclr Pri0. Closing. |
List of requests from Helix to reduce failure overhead from PayloadGroup0, which seems to be returning a non-zero exit code very often.
Runfo Tracking Issue: payloadgroup0 work item
Displaying 100 of 381 results
Build Result Summary
The text was updated successfully, but these errors were encountered: