Removing flaky tests which are not compatible configurations and not required henceforth - #1701
Open
Kaniska (Kaniska244) wants to merge 1 commit into
Open
Removing flaky tests which are not compatible configurations and not required henceforth#1701Kaniska (Kaniska244) wants to merge 1 commit into
Kaniska (Kaniska244) wants to merge 1 commit into
Conversation
Kaniska (Kaniska244)
marked this pull request as ready for review
August 3, 2026 13:58
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
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
This PR removes flaky and incompatible test configurations from the
test-all.yamlworkflow that are no longer required. These combinations were producing unreliable results or testing configurations that are not supported, adding noise to CI without providing meaningful coverage.Changes
Excluded incompatible feature / base image combinations in the test matrix:
oryxonubuntu:jammyoryxonmcr.microsoft.com/devcontainers/base:ubuntudocker-in-dockeronmcr.microsoft.com/devcontainers/base:debiandocker-outside-of-dockeronmcr.microsoft.com/devcontainers/base:debiandocker-in-dockeronmcr.microsoft.com/devcontainers/base:ubuntudocker-outside-of-dockeronmcr.microsoft.com/devcontainers/base:ubuntuSeparated
iptables-isolationscenarios out of thedocker-in-dockerjob:docker_with_default_iptablesanddocker_with_default_iptables_ubuntuscenarios fromtest/docker-in-docker/scenarios.jsonbefore running, so they run in a dedicatediptables-isolationjob instead of the general scenario run.Motivation
iptables-isolationcoverage intact by moving it to a separate, isolated job.Testing
test-allworkflow) exercises the updated matrix and confirms the excluded combinations are no longer run while remaining scenarios continue to pass.