Skip to content

Increase osx-arm64 GCStress3 timeout #114725

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

BruceForstall
Copy link
Member

No description provided.

@BruceForstall
Copy link
Member Author

/azp run runtime-coreclr gcstress0x3-gcstress0xc

Copy link

Azure Pipelines failed to run 1 pipeline(s).

Copy link
Contributor

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

@BruceForstall
Copy link
Member Author

/azp run runtime-coreclr gcstress0x3-gcstress0xc

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@BruceForstall
Copy link
Member Author

Even with this change, there are still osx-arm64 timeouts in GCStress=3 runs.

With all those runs, I see a maximum "Delay" of 23m. That doesn't seem too bad.

I see a maximum "Duration" of over 8hrs. (and killed for timeout) for a number of jobs:

Directed_2.0.1
JIT.Generics.0.1
JIT.opt.0.1
Methodical_d1.0.1
Regression_4.0.10
threading_group2.0.1

This is slightly better than before, but there is obviously still a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

1 participant