CodeVetter · Repo Unpack · Testing signals
tokio-rs/tokio
Tests and CI were inspected, not executed; no passing result is asserted. The inspected suites use Rust tests, tokio::test, trybuild, deterministic I/O mocks, and Loom concurrency modeling. CI defines nextest, separate doctests, Miri, stress testing, platform checks, and Linux-kernel-specific execution. Coverage observations are bounded: feature guards, target exclusions, and model limits prevent treating these definitions as exhaustive verification.
- tcp_echo uses tokio::test and real loopback sockets to verify repeated client round trips, split-stream copying, total byte count, and oneshot completion; Miri uses fewer iterations.
- fs_file verifies reads, flushed writes, shutdown writes, and conversion to standard files; its suite is feature-gated and excludes WASI.
- length_delimited tests use scripted framed I/O to check incomplete headers/payloads and oversized frames; separate cases verify encoding buffer growth and length-field limits.
- tests-build uses trybuild pass and compile_fail fixtures for macro argument forwarding, invalid inputs, joins, and type mismatches; the harness is ignored under Miri.
- Loom models scheduler shutdown races involving block_in_place; CI bounds exploration with two preemptions and 10,000 branches and conditionally selects suites by PR labels.
- Workspace CI runs nextest on three operating systems, repeats companion tests after removing local patches, and runs doctests separately; feature-powerset checks are limited to depth two.
- CI defines Miri with strict provenance and disabled isolation; stress-test defines release compilation and Valgrind leak checking for simple_echo_tcp.
- io-uring tests are Linux/unstable/feature-gated; CI builds filesystem and library tests for QEMU kernels, including 4.19.325, and requires a completion marker beyond failure-summary checks.