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
Add a new download-ci-llvm = if-unchanged
option and enable it by default for profile = codegen
#116881
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
This PR changes This PR changes src/bootstrap/defaults/config.codegen.toml. If appropriate, please also update |
This comment has been minimized.
This comment has been minimized.
This PR changes src/bootstrap/defaults/config.codegen.toml. If appropriate, please also update This PR changes |
This comment has been minimized.
This comment has been minimized.
By the way, triagebot.toml should be updated because the bootstrap codebase is reorganized. The tips above seem out of date. |
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.
Current PR ID(which is 116881) should be appended to this constant:
Lines 73 to 81 in 020d008
/// Keeps track of major changes made to the bootstrap configuration. | |
/// | |
/// These values also represent the IDs of the PRs that caused major changes. | |
/// You can visit `https://github.com/rust-lang/rust/pull/{any-id-from-the-list}` to | |
/// check for more details regarding each change. | |
/// | |
/// If you make any major changes (such as adding new values or changing default values), please | |
/// ensure that the associated PR ID is added to the end of this list. | |
pub const CONFIG_CHANGE_HISTORY: &[usize] = &[115898]; |
This should be replaced with the current PR ID:
Lines 22 to 33 in 020d008
# Keeps track of major changes made to this configuration. | |
# | |
# This value also represents ID of the PR that caused major changes. Meaning, | |
# you can visit github.com/rust-lang/rust/pull/{change-id} to check for more details. | |
# | |
# A 'major change' includes any of the following | |
# - A new option | |
# - A change in the default values | |
# | |
# If `change-id` does not match the version that is currently running, | |
# `x.py` will prompt you to update it and check the related PR for more details. | |
change-id = 115898 |
This comment has been minimized.
This comment has been minimized.
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.
I still need some work to confirm the second task, maybe a separate PR is needed.
I think we can handle it in this PR
…k-Simulacrum fix bootstrap paths in triagebot.toml ref #rust-lang#116881 (comment)
Rollup merge of rust-lang#116928 - onur-ozkan:update-triagebot, r=Mark-Simulacrum fix bootstrap paths in triagebot.toml ref #rust-lang#116881 (comment)
This PR modifies This PR modifies |
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #116998) made this pull request unmergeable. Please resolve the merge conflicts. |
Commit history still looks inappropriate. |
reworded it |
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.
Can you squash your commits into "Fix issue #110087" one ? Following commits alone doesn't make too much sense as far as I see. Specially the 2nd one.
Three tasks have been implemented here. Add a new `download-ci-llvm = if-unchange` option and enable if by default for `profile = codegen`. Include all build artifacts by traversing the llvm-project build output, Keep the downloadable llvm the same state as if you have just run a full source build. After selecting the codegen profile during ./x.py setup, the submodule will be automatically downloaded.
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.
Thank you for the fixes.
CC #110087
I still need some work to confirm the second task, maybe a separate PR is needed.
PR description seems to be outdated, it would be nice if you update it :) I will queue up the PR anyway.
@bors r+ rollup=iffy |
☀️ Test successful - checks-actions |
Finished benchmarking commit (750c2ec): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 663.473s -> 664.216s (0.11%) |
@@ -77,7 +77,7 @@ const LLD_FILE_NAMES: &[&str] = &["ld.lld", "ld64.lld", "lld-link", "wasm-ld"]; | |||
/// | |||
/// If you make any major changes (such as adding new values or changing default values), please | |||
/// ensure that the associated PR ID is added to the end of this list. | |||
pub const CONFIG_CHANGE_HISTORY: &[usize] = &[115898, 116998, 117435]; | |||
pub const CONFIG_CHANGE_HISTORY: &[usize] = &[115898, 116998, 117435, 116881]; |
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.
I'm getting a WARNING pointing me to this PR. Do I need to do something? Or can I keep my existing config? It's unclear to me. The PR description says there's a new config, but why does everyone have to be alerted of its existence?
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.
Also this list is unordered now, that seems wrong?
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.
update change-id = 116881
instead may be help.
AFAIK This is ordered by merge time to keep the source code synchronized with the config file.
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.
update change-id = 116881 instead may be help.
That will silence the warning, sure. But the reason the warning is shown must be that I should do something before silencing it. There's no point in having people mindlessly increment a number every week just to get rid of the latest warning.
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.
Also this list is unordered now, that seems wrong?
Lines 78 to 80 in 1db4b12
/// If you make any major changes (such as adding new values or changing default values), | |
/// please ensure that the associated PR ID is added to the end of this list. | |
/// This is necessary because the list must be sorted by the merge date. |
I'm getting a WARNING pointing me to this PR. Do I need to do something? Or can I keep my existing config? It's unclear to me
rust/src/bootstrap/defaults/config.codegen.toml
Lines 12 to 13 in 1db4b12
# build llvm from source | |
download-ci-llvm = "if-unchanged" |
PR updated the default value here. I am pretty sure we have people who wants to know this change.
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.
Then the PR description needs to say: "if you are coming here from x.py, here's what do do: if you are using the 'codegen' profile, be aware that the default value changed. otherwise, you can ignore this".
Currently I'm coming here clueless and wasting 5min trying to figure out if I should do something, before giving up, frustrated.
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.
That's my bad, I will add the description for this PR later
For this PR I am also confused why we have if-available and if-unchanged as two different options. When would I ever want if-available? Shouldn't if-unchanged just be the default everywhere, since it will "do the right thing" in most situations? |
If there is no need to modify llvm locally,
Is it similar to this? https://github.com/orgs/rust-lang/projects/35/views/1?pane=issue&itemId=40227883 |
Have you measured it? How long does the change-check take? We also have |
Not yet, the change-check is based on |
This comment became obsolete after rust-lang#116881 switched over to `download-ci-llvm = "if-unchanged"`.
This comment became obsolete after rust-lang#116881 switched over to `download-ci-llvm = "if-unchanged"`.
Three tasks have been implemented here.
Add a new
download-ci-llvm = if-unchange
option and enable if bydefault for
profile = codegen
.Include all build artifacts by traversing the llvm-project build output,
Keep the downloadable llvm the same state as if you have just run a full
source build.
After selecting the codegen profile during ./x.py setup, the submodule
will be automatically downloaded.
It should be noted that:
if you are using the 'codegen' profile, be aware that the default value changed. otherwise, you can ignore this.
Resolves #110087