Skip to content
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

Increase Arm64 test build timeout #44595

Merged
merged 3 commits into from
Nov 2, 2024

Conversation

MiYanni
Copy link
Member

@MiYanni MiYanni commented Nov 1, 2024

Summary

As a follow-up to this PR where we added the Arm64 test build, I notice it regularly times out. I think it is on the cusp of hitting the 60 45 minute default timeout for a Helix run, so it sometimes takes longer and sometimes doesn't. So, I decided to up the timeout to 90 60 minutes. If we hit the timeout period after this change, then there is probably a bigger concern.

I will also forwardport this to main.

@MiYanni MiYanni requested a review from a team November 1, 2024 20:41
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Request triage from a team member labels Nov 1, 2024
@MiYanni
Copy link
Member Author

MiYanni commented Nov 1, 2024

@joeloff @dsplaisted It seems I set the wrong timeout. I need to figure out how to set the timeout inside the Helix run itself; not for the job. The job default timeout is actually 150 minutes. So, let me look that up and I'll update the PR.

Looking at the Helix logs, they do:

dotnet exec Microsoft.NET.Build.Tests.dll -e HELIX_WORK_ITEM_TIMEOUT=00:45:00

Edit: Found where it is set:

<XUnitWorkItemTimeout>00:45:00</XUnitWorkItemTimeout>

@MiYanni MiYanni merged commit 2678a15 into dotnet:release/9.0.2xx Nov 2, 2024
32 checks passed
@MiYanni MiYanni deleted the IncreaseArm64Timeout branch November 2, 2024 00:18
@MiYanni
Copy link
Member Author

MiYanni commented Nov 2, 2024

/backport to main

Copy link
Contributor

github-actions bot commented Nov 2, 2024

Started backporting to main: https://github.com/dotnet/sdk/actions/runs/11638170341

Copy link
Contributor

github-actions bot commented Nov 2, 2024

@MiYanni backporting to main failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Applying: Increased the timeout for Arm64 test builds to 90 minutes.
Using index info to reconstruct a base tree...
M	.vsts-ci.yml
M	.vsts-pr.yml
Falling back to patching base and 3-way merge...
Auto-merging .vsts-pr.yml
CONFLICT (content): Merge conflict in .vsts-pr.yml
Auto-merging .vsts-ci.yml
CONFLICT (content): Merge conflict in .vsts-ci.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Increased the timeout for Arm64 test builds to 90 minutes.
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

Copy link
Contributor

github-actions bot commented Nov 2, 2024

@MiYanni an error occurred while backporting to main, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants