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

Adjust timeout on helix runs to 15 minutes to ensure dumps are captur… #61001

Merged
merged 1 commit into from
Apr 28, 2022

Conversation

dibarbet
Copy link
Member

…ed within the 30minute timeout of a helix run

See - #57549 (comment)

Was changed in #59783 to fix integration tests, but we should keep the old timeout for helix jobs.

…ed within the 30minute timeout of a helix run
@dibarbet dibarbet requested a review from a team as a code owner April 27, 2022 23:05
@dibarbet dibarbet enabled auto-merge (squash) April 27, 2022 23:23
Comment on lines +90 to 91
// The 25 minute timeout in integration tests accounts for the fact that VSIX deployment and/or experimental hive reset and
// configuration can take significant time (seems to vary from ~10 seconds to ~15 minutes), and the blame
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When we originally made this change we later discovered we were having other issues that was causing VSIX deployment to hang -- it'd be interesting to actually see if we actually can move it back to 15 minutes for everything.

@dibarbet dibarbet merged commit 6f01312 into dotnet:main Apr 28, 2022
@ghost ghost added this to the Next milestone Apr 28, 2022
@dibarbet dibarbet deleted the fix_dump_timeout_helix branch April 29, 2022 00:38
@Cosifne Cosifne modified the milestones: Next, 17.3 P2 May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants