Enforcement of cascaded failures in CI #20180
BillyONeal
started this conversation in
Ideas
Replies: 1 comment
-
PS. This will also effectively provide a fix for #13533 when implemented. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is a continued discussion from #20074 (comment)
Pending things:
Add validation for the preceding number and fail PRs if the number of cascades change. Then at least git blame will find PRs that had to make significant edits here.Add "cascades" enforcement #20140=cascade
or similar to ci.baseline.txt. This probably requires moving parsing of that file into vcpkg.exe rather than a preprocessing script. (Probably @BillyONeal but not on the top of priority list for now)Experience notes:
Unfortunately we were forced to disable the cascade count check because:
Backing that out is #20181
We still think the =cascade plan can work but we are hoping there are better answers here...
/cc @dg0yt @cenit
Beta Was this translation helpful? Give feedback.
All reactions