mirror of
https://github.com/tokio-rs/tokio.git
synced 2025-09-25 12:00:35 +00:00

- Pass `--no-deps` to `cargo-clippy` - Use `dtolnay/rust-toolchain@stale` instead of `dtolnay/rust-toolchain@master` - Use dtolnay/rust-toolchain instead of `rustup` directly - Use `cargo-nextest` in job test to speedup testing - Use `cargo-nextest` in job test-unstable to speedup testing - Use `cargo-nextest` in job test-unstable-taskdump to speedup testing - Use `cargo-nextest` in job no-atomic-u64 to speedup testing - Use `cargo-nextest` in job check-unstable-mt-counters - Run `cargo check --benches` for `benches/` in job test Since the benchmark is not run - Run `cargo-check` instead of `cargo-build` in job test-parking_lot since no test is run - Run `cargo-check` instead of `cargo-build` in job no-atomic-u64 - Run `Swatinem/rust-cache@v2` after `taiki-e/install-action@v2` to avoid caching pre-built artifacts downloaded by it. - Use `Swatinem/rust-cache@v2` in job no-atomic-u64 - Add concurrenty group to cancel outdated CI - Use `taiki-e/setup-cross-toolchain-action@v1` in job cross-test instead of cross, so that we can use `cargo-nextest` to run tests in parallel. Also use `Swatinem/rust-cache@v2` to cache artifacts. - Use `Swatinem/rust-cache@v2` in job cross-check to speedup ci. - Fix job `cross-test`: Use `armv5te-unknown-linux-gnueabi` for no-atomic-u64 testing instead of `arm-unknown-linux-gnueabihf`, which actually has atomic-u64 - Rm use of `cross` in job `cross-check` Since it does not run any test, it does not need the `cross-rs` toolchain as tokio does not use any external C/C++ library that require `gcc`/`clang` to compile. - Add more recognizable name for steps in job cross-test - Split job `test` into `test-{tokio-full, workspace-all-features, integration-tests-per-feature}` - Split job `no-atomic-u64` into `no-atomic-u64-{test, check}` - Parallelize job `features` by using matrix - Split `cross-test` into `cross-test-{with, without}-parking_lot` - Speedup job `cross-test-*` and `no-atomic-u64-test` by running `cargo-test` with `-- --test-threads 1` since `qemu` userspace emulation has problems running binaries with many threads. - Speedup workflow `stress-test.yml` and job `valgrind` in workflow `ci.yml` by passing `--fair-sched=yes` to `valgrind`. - Speedup job `test-hyper`: Cache `./hyper/target` instead of caching `./target`, which is non-existent. - Set `RUST_TEST_THREADS=1` to make sure `libtest` only use one thread so that qemu will be happy with the tests. This is applied to `cross-test-with(out)-parking_lot, no-atomic-u64-test`. - Apply suggestions from code review Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>