-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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.
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
Cargotest enhancements #70659
Comments
CargoTest SummaryWhat is Cargotest?
Goal of Cargotest
How does Cargotest work?
What does Cargotest test right nowLibrariesCLI appsBig production code basesWhat do we still need to decide?
Useful LinksCode LinksDiscussions on this topic |
Problems with Cargotest
|
Requirements for a project to be included in Cargotest
Possible projects to include(This list is based on libraries that are already tested with Cargotest (and fit the above requirements), the most commonly used libraries as found by the 2019 State or Rust Survey, and in this Discord conversation LibrariesCLI appsBig production code basesAsyncTo Do
|
cargotest: do not run quickcheck tests in xsv Fixes rust-lang#73514 I know rust-lang#70659 discusses a larger overhaul of cargotest, but that seems to have stalled and I'd like to fix the immediate issue of PRs failing due to random test failures in xsv. This still runs the vast majority of tests by numbers: ``` test result: ok. 394 passed; 0 failed; 0 ignored; 0 measured; 32 filtered out; finished in 1.84s ``` So the loss in test coverage is hopefully not too big.
Triage: I'm not sure what the current status of this initiative is. UPD: asked in https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Who's.20maintaining.20cargotest.3F, not actively maintained but isn't causing too many issues. |
The Infra team recently made some decisions around the future of cargotest - and there is more to decided and implemented. This issue tracks this work.
Reference: https://paper.dropbox.com/doc/The-future-of-cargotest--AxQ6EFIbNcslFkGPv4Kbr8yhAg-KuqIf3UWJnfrfrukx8o4G
The text was updated successfully, but these errors were encountered: