#cargo #flaky

app cargo-flaky

A cargo sub-command to helps you find flaky tests

5 unstable releases

0.3.1 Jun 15, 2021
0.3.0 Jun 14, 2021
0.2.1 Jun 8, 2021
0.1.1 Jun 3, 2021

#406 in Cargo plugins

Download history 22/week @ 2023-07-12 24/week @ 2023-07-19 24/week @ 2023-07-26 23/week @ 2023-08-02 23/week @ 2023-08-09 38/week @ 2023-08-16 29/week @ 2023-08-23 32/week @ 2023-08-30 32/week @ 2023-09-06 22/week @ 2023-09-13 22/week @ 2023-09-20 25/week @ 2023-09-27 25/week @ 2023-10-04 18/week @ 2023-10-11 19/week @ 2023-10-18 28/week @ 2023-10-25

90 downloads per month

MIT license

392 lines

cargo flaky

Cargo flaky extends cargo to help you find flaky tests in you test suite, and help you solve them.


Flaky tests are notoriously annoying and difficult to debug, because of their very nature: they seem to happen randomly. The idea behind cargo edit is to run you test a great number of times to try to trigger failure of those flaky tests. But this is not sufficient, because knowing that the bug exists is rarely sufficient to debug it, cargo flaky also allows you to record the failing tests using rr, so you can play back the execution of your tests when they failed. Noice.


from source:

git clone https://github.com/MarinPostma/cargo-flaky.github
cd cargo flaky
cargo install --path .


Right now, cargo flaky doesn't support passing custom arguments to the test suite.

You can run all your tests an arbitrary number of times:

cargo flaky -i 30 # run your test suite 30 times and collect all failures

And you can record your failing test (require rr to be installed)

cargo flaky -i 30 -r # run your tests suite 30 time and record failures


--- Found 1 failing test ---

test: test::test stdout, 10/10 (100%)
Test binary: /home/mpostma/Documents/code/rust/cargo-flaky/target/debug/deps/cargo_flaky-2ac6d6022fd
thread 'main' panicked at 'explicit panic', src/main.rs:231:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

recording available in : recording_20210603213043/record_iter_1

You can now run rr replay recording_20210603213043/record_iter_1 to open a gdb session and debug a recording of the failing test instance.

You can get more usage information by typing cago flaky --help.


This is still a work in progress, and lacks many features. Do not hesitate to open a PR/issue if you're missing something.




~252K SLoC