Handle some flaky ProjectAnalysisTests cases#18200
Merged
Merged
Conversation
Contributor
✅ No release notes required |
T-Gro
approved these changes
Jan 6, 2025
0101
approved these changes
Jan 6, 2025
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Contributor
|
This PR is particularly unlucky... |
Contributor
Author
|
Ah, this particular failure is unrelated but a genuine bug. I'll sort it out. |
Contributor
|
Thanks @majocha for your continuous interest 😎 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Description
Test cases utilizing
Project25do not like to run concurrently with each other. Probably because of theXmlProviderhere:fsharp/tests/FSharp.Compiler.Service.Tests/ProjectAnalysisTests.fs
Lines 3666 to 3675 in 749853e
I verified locally by running some iterations that marking the affected test cases with
RunTestCasesInSequenceresolves the problem.