-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
stabilize ci_rustc_if_unchanged_logic
test for local environments
#138245
base: master
Are you sure you want to change the base?
Conversation
73bca58
to
1452b11
Compare
This comment has been minimized.
This comment has been minimized.
a592504
to
e441c97
Compare
Signed-off-by: onur-ozkan <[email protected]>
e441c97
to
5c1c83c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, the test fix LGTM. I have one suggestion re. how to make this test less likely to diverge in the future.
config.last_modified_commit(&["compiler", "library"], "download-rustc", true).is_none(); | ||
let mut paths = vec!["compiler"]; | ||
|
||
// Handle library tree the same way as in `Config::download_ci_rustc_commit`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: I think we should either:
- Have a single source of truth for the paths calculation fed to
last_modified_commit
for this purpose, - Or at least add a comment at the source site where we also do this paths adjustment to remind also updating this test.
wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have a single source of truth for the paths calculation fed to last_modified_commit for this purpose,
We can't do that as one side excludes those paths and the other includes them. Also, using that approach would cause this coverage to miss the expected behaviour (imagine that function somehow have bugs in its logic).
Or at least add a comment at the source site where we also do this paths adjustment to remind also updating this test.
Sure, let me know exactly where and what you want me to write.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe just cc this test next to https://github.com/rust-lang/rust/blob/master/src%2Fbootstrap%2Fsrc%2Fcore%2Fconfig%2Fconfig.rs#L2984-L2990?
@rustbot author |
Fixes #138239