Skip to content

[TIMING] debug output does not distinguish checking from building #96060

Closed
@jyn514

Description

@jyn514

While debugging the CI failure in #95450, I saw the following output in the logs:

2022-04-13T11:24:41.1948979Z [TIMING] Rustc { stage: 2, target: TargetSelection { triple: "x86_64-unknown-linux-gnu", file: None } } -- 113.867
2022-04-13T11:25:13.1594039Z [TIMING] Rustc { target: TargetSelection { triple: "x86_64-unknown-linux-gnu", file: None } } -- 31.963

The first one is doc::Rustc and the second I think is check::Rustc, by the fields it has. But we should just print that in the debug logs rather than having to guess.

@rustbot label +A-contributor-roadblock +C-enhancement

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-contributor-roadblockArea: Makes things more difficult for new or seasoned contributors to RustC-enhancementCategory: An issue proposing an enhancement or a PR with one.E-mediumCall for participation: Medium difficulty. Experience needed to fix: Intermediate.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.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