Skip to content
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.

Sign up for GitHub

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

Jump to bottom

libtest: utilize jobserver #48532

Open
ishitatsuyuki opened this issue Feb 25, 2018 · 1 comment
Open

libtest: utilize jobserver #48532

ishitatsuyuki opened this issue Feb 25, 2018 · 1 comment
Labels
A-libtest Area: `#[test]` / the `test` library C-feature-request Category: A feature request, i.e: not implemented / a PR. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@ishitatsuyuki
Copy link
Contributor

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
@estebank estebank added the A-libtest Area: `#[test]` / the `test` library label Feb 25, 2018
@ishitatsuyuki ishitatsuyuki mentioned this issue Mar 8, 2018
Closed
@XAMPPRocky XAMPPRocky added C-enhancement Category: An issue proposing an enhancement or a PR with one. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels May 14, 2018
@Mark-Simulacrum Mark-Simulacrum added T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. and removed T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Jun 3, 2018
@jonas-schievink jonas-schievink added C-feature-request Category: A feature request, i.e: not implemented / a PR. and removed C-enhancement Category: An issue proposing an enhancement or a PR with one. labels Apr 20, 2020
@epage epage mentioned this issue Jun 3, 2023
Open
@gilescope
Copy link
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-libtest Area: `#[test]` / the `test` library C-feature-request Category: A feature request, i.e: not implemented / a PR. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
testing-devex backlog
Status: No status
Milestone
No milestone
Development

No branches or pull requests
6 participants
@gilescope @estebank @jonas-schievink @XAMPPRocky @Mark-Simulacrum @ishitatsuyuki