-
Notifications
You must be signed in to change notification settings - Fork 221
Ensure that packages that are both changed AND part of the AdditionalValidationPackages set are handled properly #9635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure that packages that are both changed AND part of the AdditionalValidationPackages set are handled properly #9635
Conversation
… are NOT counted as 'includedForValidation: true' if they also exist in the original 'these packages changed' set
|
The following pipelines have been queued for testing: |
Co-authored-by: Ben Broderick Phillips <[email protected]>
|
The following pipelines have been queued for testing: |
Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#9635 See [eng/common workflow](https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/README.md#workflow) --------- Co-authored-by: Scott Beddall <[email protected]> Co-authored-by: Scott Beddall <[email protected]> Co-authored-by: Ben Broderick Phillips <[email protected]>
…ValidationPackages set are handled properly (Azure#9635) * ensure that packages that come back from AdditionalValidationPackages are NOT counted as 'includedForValidation: true' if they also exist in the original 'these packages changed' set Co-authored-by: Ben Broderick Phillips <[email protected]> --------- Co-authored-by: Ben Broderick Phillips <[email protected]>
The issue this PR is resolving is highlighted in this pr step
Note that we're saying
However, due to the order of operations, we resolve the set of
directchanged packages first, then we walk each of them checking to see if there are additional packages that they should also include if they are changed. In the example PR above, we directly changedazure-core-opencensus, but because it was also anadditionalValidationPackageforazure-core, it was getting marked as anindirectpackage. This PR fixes our logic so that if a package is directly changed, we always count is as such, instead of accidentally overriding and claiming it is anincludedForValidationpackage.