Disable flakey container registry tests #49686
Closed
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
These tests have a high number of failures documented at (Skip = "dotnet#49502"). The registry issue may not be solved until funding is increased or engineering effort is made to handle this case better and not run the tests. Merge
we will still find this in search and with the history of test-debt label. Lets just do this temporary workaround
nagilson
added
Area-Containers
Member
Member
Author
|
Awesome, thank you |
Member
Author
|
The ACR issue is resolved but there is a new issue with docker being out of date on the machines which is still causing failures. In the worst case if dnceng is not able to update the images, then we may want to do this again |
This was referenced Jul 8, 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.
These tests have a high number of failures documented at (Skip = "#49502").
The registry issue may not be solved until funding is increased or engineering effort is made from the containers side to handle this case better and not run the tests. But right now it is blocking everything in the repo.