-
Notifications
You must be signed in to change notification settings - Fork 24
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
Add various options #42
Conversation
Note that errors on nightly are ignored, because nightly is unpredictable. Fixes #37
cc @djc |
Awesome! |
Codecov Report
@@ Coverage Diff @@
## master #42 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 1 1
Lines 5 5
=====================================
Hits 5 5
Continue to review full report at Codecov.
|
Pushed one more option that enables you to skip |
We need support for _not_ running with `--all-features` due to the nightly requirement for async/await which is enabled by a feature in `tracing`. This will eventually land with crate-ci/azure-pipelines#42.
* First draft of Azure Pipelines CI config You'll have to follow the instructions over at https://github.com/crate-ci/azure-pipelines to get it fully set up. Might also run into some weirdness with having to change the "default" branch once merged. But 🎉 Oh, yeah, and need to also update Cargo.toml, README badge, etc. * Also check benchmarks * Pool is set per job, not per stage * Not a template anymore * Use correct service connection name * Disable readme doctest pending rewrite * Fully remove old doctest readme * Don't run cargo check yet We need support for _not_ running with `--all-features` due to the nightly requirement for async/await which is enabled by a feature in `tracing`. This will eventually land with crate-ci/azure-pipelines#42. * Hack dependency chain Closes #177
Brings back `cargo check` as discussed here: #191 (comment) now that crate-ci/azure-pipelines#42 has landed.
This PR adds support for a few requested features (#37 and #41), as well as for running tests single-threaded (
--test-threads=1
), which some projects need.