ChadNedzlek
commented
2 years ago So this is... interesting. I agree this seems like essentially a random network failure that is not the fault of the code. Also... it doesn't seem like there is anything to be done other than retry the build.
@ulisesh and @AlitzelMendez. This seems like another instance of a "known issue" that would really benefit from the ability to get retried automatically. I think Carlos did the right thing by opening the known issue, but his PR (and any future PR that hits this) is still going to be blocked, since the build doesn't run at all in this case, because the checkout failed. And it would be great to help folks that hit this.
ulisesh
markwilkie
ViktorHofer
premun
dougbu
carlossanlop
AlitzelMendez
Build
https://dev.azure.com/dnceng/public/_build/results?buildId=1706886&view=results
Build leg reported
Libraries Test Run release coreclr Linux_musl x64 Release
Pull Request
Rolling build for runtime
Action required for the engineering services team
To triage this issue (First Responder / @dotnet/dnceng):
If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:
Edit this issue and add an error string in the Json below that can help us match this issue with future build breaks. You should use the known issues documentation
Additional information about the issue reported
The
Checkout dotnet/runtime@main to sstep is the one that failed. Here is the end of the log output:Report
Displaying 100 of 102 results
Summary
Known issue validation
Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=323960 Error message validated:
Git fetch failed with exit code: 128Result validation: :white_check_mark: Known issue matched with the provided build. Validation performed at: 6/28/2023 9:15:14 PM UTC