Open
Conversation
This was turning into something worthy of its own PR so I put it back to how it was before to work on next/separately
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, Motivation and Context
Instead of running every test for all changes, this aims to run only tests that are relevant to the changes made in a pull request. For example if a PR introduces changes to collectors, it would run preflight and support bundle tests since both are affected, however if a change is only made to preflight, only preflight tests would be run.
The reason behind this is to reduce time spent on waiting for tests to run and pass or fail as there are many situations where not every single test needs to be run
Checklist
Does this PR introduce a breaking change?