docs(readme): add cargo test instructions#760
Conversation
|
A similar error appeared during the CI runs of #748, which caused some confirmation bias: I thought that only I can also modify the CI pipelines so as to use the --no-fail-fast flag after discussing and getting a positive signal on this PR. |
|
Related: #726 (comment) |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #760 +/- ##
=======================================
Coverage 67.45% 67.45%
=======================================
Files 20 20
Lines 2338 2338
=======================================
Hits 1577 1577
Misses 761 761 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I came across a mysterious error that affected fs-test. As I was experimenting with code affecting file reads and writes, I falsely assumed that the issue was isolated to this test in particular. I forgot that the rest of the tests would not get executed if the first one were to fail.
8a6f13f to
188a96e
Compare
|
Hmm, honestly: I think this is rather verbose. The essence of this change is the If you think the Please don't hesitate to re-open if you disagree. |
|
You can also add that flag to the CI. That might be of value. |
I came across a mysterious error that affected fs-test.
As I was experimenting with code affecting file reads and writes, I falsely assumed that the issue was isolated to this test in particular. I forgot that the rest of the tests would not get executed if the first one were to fail.