libtest: utilize jobserver #48532
Copy link
Copy link
Open
Labels
A-libtestArea: `#[test]` / the `test` libraryArea: `#[test]` / the `test` libraryC-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.T-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Description
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
Reacted by Squirrel
Metadata
Metadata
Assignees
Labels
A-libtestArea: `#[test]` / the `test` libraryArea: `#[test]` / the `test` libraryC-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.T-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Type
Projects
- StatusShow more project fieldsNo status
Activity
gilescope commentedon Jun 3, 2023
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.