fix: actually tests finish_edge must fire once per edge - #559
Conversation
|
Boost dependency footprint vs Header-inclusion weights (graph files pulling each direct dependency in): No header-inclusion-weight changes. Transitive Boost modules: 68 → 68 (0) |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #559 +/- ##
===========================================
+ Coverage 88.22% 92.82% +4.60%
===========================================
Files 392 391 -1
Lines 27412 28173 +761
Branches 7997 7996 -1
===========================================
+ Hits 24183 26151 +1968
- Misses 1881 1917 +36
+ Partials 1348 105 -1243
... and 287 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
Compiler-warning counts vs
|
An old test file testing an old bug does not assert anything. Now solved, and the file has been folded into
dfs.cppBefore submitting
developbranch.Type of change
Does this PR introduce a breaking change?
What this PR does
finish_edge_bug.cppintodfs.cppastest_finish_edge_is_called()Motivation
Flickering CI coverage. Tests should not output only.
Testing
Checklist
b2in thetest/directory).