Skip to content

libtest: utilize jobserver #48532

Open
Open

Description

@ishitatsuyuki

Tests are normally CPU consuming tasks, and we can transparently utilize jobserver to achieve efficient core utilization.

Some usecases I can think of:

  • Tests which may spawn threads (including rustc codegen-units, but not limited to)
  • Using a parent make somewhere

Activity

  1. added
    C-enhancementCategory: An issue proposing an enhancement or a PR with one.
    T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.
    on May 14, 2018
  2. added
    T-libs-api[DEPRECATED; DO NOT USE]
    and removed
    T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.
    on Jun 3, 2018
  3. added
    C-feature-requestCategory: A feature request, i.e: not implemented / a PR.
    and removed
    C-enhancementCategory: An issue proposing an enhancement or a PR with one.
    on Apr 20, 2020
  4. gilescope commented on Jun 3, 2023

    @gilescope
    Contributor

    Not having this was the reason why Alex said that parallel test running PRs could not be accepted into cargo, so this would unblock parallel testing across multiple crates.

  5. added
    T-libsRelevant to the library team, which will review and decide on the PR/issue.
    and removed
    T-libs-api[DEPRECATED; DO NOT USE]
    on Aug 12, 2026
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-libtestArea: `#[test]` / the `test` libraryC-feature-requestCategory: A feature request, i.e: not implemented / a PR.T-libsRelevant to the library team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions