Disable automatic test discovery for Roslyn in DevKit #73878
Merged
Conversation
This file contains 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
…fails due to locked files during discovery
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
dibarbet
changed the title
dibarbet
changed the title
jaredpar
approved these changes
Jun 6, 2024
This was referenced Jun 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Keep hitting the same issue @jaredpar hit a while back - where the testhost locks files and causes the build to fail.
This disables automatic discovery using the option added in microsoft/vscode-dotnettools#1089
Discovery can be run manually by hitting the refresh button in the test explorer.