Deal with a hanging test #18411
Merged
Deal with a hanging test #18411
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ No release notes required |
T-Gro
approved these changes
Mar 26, 2025
github-project-automation
bot
moved this from New
to In Progress
in F# Compiler and Tooling
github-project-automation
bot
moved this from In Progress
to Done
in F# Compiler and Tooling
T-Gro
added a commit
that referenced
this pull request
Mar 26, 2025
* update devcontainer sdk (#18412) * deal with hanging test (#18411) * typo (#18413) --------- Co-authored-by: Martin <[email protected]> Co-authored-by: Jakub Majocha <[email protected]> Co-authored-by: Kevin Ransom (msft) <[email protected]>
This was referenced Apr 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CompilerService.AsyncMemoize.Cancel running jobs with the same keytest likes to hang sometimes:https://dev.azure.com/dnceng-public/public/_build/results?buildId=993075&view=logs&j=09cc464c-89cd-5758-006d-ba9e3958cfa9&t=098678ff-b2f3-5c88-44d3-4c7be2f47e75&l=9207
This should fix it or at least produce a proper test failure if it happens again.