-
Notifications
You must be signed in to change notification settings - Fork 13.4k
bootstrap: only show PGO warnings when verbose #117982
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Building rustc with `--rust-profile-use` is currently dumping a lot of warnings of "no profile data available for function" from `rustc_smir` and `stable_mir`. These simply aren't exercised by the current profile- gathering steps, but that's to be expected for new or experimental functionality. I think for most people, these warnings will be just noise, so it makes sense to only have them in verbose builds.
r? @onur-ozkan (rustbot has picked a reviewer for you, use r? to override) |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Those failures are "warning: spurious network error". |
These warnings are indeed a bit annoying on CI, but I still think that it would be nice if we saw the PGO warnings in CI logs, to spot potential PGO regressions. So I would prefer either filtering only some of the crates (probably hard to do), or make sure that we use verbose builder on CI? 🤔 |
@bors r+ |
Enabling verbose mode on CI shouldn't cause any harm I think. If we're not already doing so, we should consider turning it on.
This should definetly be handled with turning the verbosity instead of printing the logs by default. |
…iaskrgr Rollup of 5 pull requests Successful merges: - rust-lang#117892 (Detect more `=>` typos) - rust-lang#117959 (Better handle type errors involving `Self` literals) - rust-lang#117980 (fix: Update CONTRIBUTING.md recommend -> recommended) - rust-lang#117982 (bootstrap: only show PGO warnings when verbose) - rust-lang#117990 (Tweak error and move tests) Failed merges: - rust-lang#117944 (some additional region refactorings) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#117982 - cuviper:quiet-pgo, r=onur-ozkan bootstrap: only show PGO warnings when verbose Building rustc with `--rust-profile-use` is currently dumping a lot of warnings of "no profile data available for function" from `rustc_smir` and `stable_mir`. These simply aren't exercised by the current profile- gathering steps, but that's to be expected for new or experimental functionality. I think for most people, these warnings will be just noise, so it makes sense to only have them in verbose builds.
Building rustc with
--rust-profile-use
is currently dumping a lot ofwarnings of "no profile data available for function" from
rustc_smir
and
stable_mir
. These simply aren't exercised by the current profile-gathering steps, but that's to be expected for new or experimental
functionality. I think for most people, these warnings will be just
noise, so it makes sense to only have them in verbose builds.