Skip to content

Make the status messages emitted by bootstrap more clear #102003

Closed

Description

@jyn514

I'm currently having an extended discussion in https://rust-lang.zulipchat.com/#narrow/stream/326414-t-infra.2Fbootstrap/topic/Stage.20numbering.20for.20tools about what the stage numbering for bootstrap means and how it should work. Part of the confusion, as pointed out by @the8472, is that it's unclear whether "Building stage1 std artifacts" refers to the compiler being run or the artifact being created. We should make this more clear by printing "Building stage1 std using stage0-sysroot".

(the names are kind of weird for now; #101961 will help with this.)

Activity

  1. added
    T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
    E-mediumCall for participation: Medium difficulty. Experience needed to fix: Intermediate.
    A-contributor-roadblockArea: Makes things more difficult for new or seasoned contributors to Rust
    on Sep 19, 2022
  2. jyn514 commented on Sep 19, 2022

    @jyn514
    MemberAuthor

    This is "easy" but a lot of work; these messages are printed in a lot of different places across bootstrap and it's going to be a lot of manual work to update them all. #86022 had some WIP effort to make the status message autogenerated, but that will likely be even more work than updating the messages by hand.

  3. self-assigned this
    on Nov 5, 2022
  4. added a commit that references this issue on Nov 6, 2022
  5. added a commit that references this issue on Nov 12, 2022
  6. added a commit that references this issue on Nov 13, 2022
  7. removed their assignment
    on Dec 20, 2022
  8. jyn514 commented on Dec 20, 2022

    @jyn514
    MemberAuthor

    An example change:

    diff --git a/src/bootstrap/tool.rs b/src/bootstrap/tool.rs
    index 24b033cc0dc..b8ea072e584 100644
    --- a/src/bootstrap/tool.rs
    +++ b/src/bootstrap/tool.rs
    @@ -70,7 +70,17 @@ fn run(self, builder: &Builder<'_>) -> Option<PathBuf> {
                 &self.extra_features,
             );
     
    -        builder.info(&format!("Building stage{} tool {} ({})", compiler.stage, tool, target));
    +        let msg = if self.mode == Mode::ToolRustc {
    +            format!(
    +                "Building stage {} tool {tool} using stage {} sysroot ({target})",
    +                compiler.stage + 1,
    +                compiler.stage
    +            )
    +        } else {
    +            format!("Building tool {tool} using stage {} sysroot ({target})", compiler.stage)
    +        };
    +        builder.info(&msg);
    +
             let mut duplicates = Vec::new();
             let is_expected = compile::stream_cargo(builder, cargo, vec![], &mut |msg| {
                 // Only care about big things like the RLS/Cargo for now
  9. jyn514 commented on Apr 29, 2023

    @jyn514
    MemberAuthor

    fixed in #108171 (lol apparently i opened the same issue twice)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-contributor-roadblockArea: Makes things more difficult for new or seasoned contributors to RustE-mediumCall for participation: Medium difficulty. Experience needed to fix: Intermediate.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions