| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Codecov Report❌ Patch coverage is 93.38843% with 8 lines in your changes missing coverage. Please review.
@@ Coverage Diff @@
## main #794 +/- ##
=======================================
Coverage 92.15% 92.15%
=======================================
Files 35 35
Lines 7377 7457 +80
Branches 383 384 +1
=======================================
+ Hits 6798 6872 +74
- Misses 438 442 +4
- Partials 141 143 +2 ☔ View full report in Codecov by Harness.
|
Sorry, something went wrong.
|
Commit 017bea8 has test result changes: GNU findutils testsuite: Test results comparison: Current: TOTAL: 495 / PASSED: 413 / FAILED: 81 / SKIPPED: 1 Reference: TOTAL: 495 / PASSED: 417 / FAILED: 77 / SKIPPED: 1 Changes from main branch: TOTAL: +0 PASSED: -4 FAILED: +4 New test failures (4): - idef-s26-0 - s14 - s14-0 - s42 bfs testsuite: Test results comparison: Current: TOTAL: 314 / PASSED: 267 / FAILED: 41 / SKIPPED: 6 Reference: TOTAL: 314 / PASSED: 267 / FAILED: 41 / SKIPPED: 6 New test failures (1): - gnu/files0_from_ok Test improvements (1): + gnu/okdir_path_empty |
Sorry, something went wrong.
Merging this PR will not alter performance✅ 20 untouched benchmarks Performance Changes
Comparing push-zlxwkxlkpsls (3ec89f4) with main (2a3eac9) |
Sorry, something went wrong.
|
could you please fix the conflicts? thanks |
Sorry, something went wrong.
Done — main is merged into push-zlxwkxlkpsls and the conflicts are resolved. Conflicts and how they were resolved
main's rework of the whitespace-delimited argument reader (the new in_argument tracking) merged cleanly and is preserved unchanged. Verification
One note from that local run: parallel_p2 is by far the heaviest benchmark (~207 ms locally vs ~3.5 ms for parallel_p8), which matches the expectation that two spinning workers are the worst case for the spin lock. The upcoming CI report will give the reference numbers on the CodSpeed runners. Summary
Was this response helpful? React with 👍 or 👎 to help us improve CodSpeedBot. |
Sorry, something went wrong.
Resolve conflicts in src/xargs/mod.rs (keep the rayon imports alongside the new strip_errno error formatting, and keep the Send bound on the argument reader required by the parallel path) and in tests/test_xargs.rs (keep both the new parallel tests and the argument-splitting tests from main).
|
Commit 3ec89f4 has test result changes: GNU findutils testsuite: Test results comparison: Current: TOTAL: 495 / PASSED: 417 / FAILED: 77 / SKIPPED: 1 Reference: TOTAL: 495 / PASSED: 421 / FAILED: 73 / SKIPPED: 1 Changes from main branch: TOTAL: +0 PASSED: -4 FAILED: +4 New test failures (4): - idef-s26-0 - s14 - s14-0 - s42 bfs testsuite: Test results comparison: Current: TOTAL: 316 / PASSED: 273 / FAILED: 37 / SKIPPED: 6 Reference: TOTAL: 317 / PASSED: 274 / FAILED: 37 / SKIPPED: 6 Changes from main branch: TOTAL: -1 PASSED: -1 FAILED: +0 No result in this run (1) - hung, crashed, or renamed: ? posix/o (was PASS) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Add CodSpeed benchmarks for the parallel xargs -P path
This PR introduces parallel execution for xargs -P (via rayon), but the existing benchmark suite (benches/xargs_bench.rs) only exercised the serial path — so CodSpeed reported the new code as untouched.
This change extends benches/xargs_bench.rs with three benchmarks that drive the new rayon-based dispatch in process_input:
Implementation notes
All benchmarks build and run successfully under codspeed run --mode simulation.