-
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
Update timeout for sourcebuild #61436
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsReact to VM changes killing official builds.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #61378 |
/backport to release/6.0-maui |
Started backporting to release/6.0-maui: https://github.com/dotnet/runtime/actions/runs/1531584872 |
@directhex backporting to release/6.0-maui failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Update timeout for sourcebuild
Using index info to reconstruct a base tree...
M eng/pipelines/runtime-official.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/runtime-official.yml
CONFLICT (content): Merge conflict in eng/pipelines/runtime-official.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update timeout for sourcebuild
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
(cherry picked from commit f9e0256)
React to VM changes killing official builds.