uutils/sed - CodSpeed

sed

Blog Docs Changelog

Performance History

Latest Results

fix: rewrite GNU testsuite harness to run upstream test scripts directly The previous harness tried to extract sed commands from GNU test scripts via regex pattern matching, which produced false negatives (comparing against empty expected output) and false positives. This led to inflated test counts and unreliable pass/fail signals. The new approach: - Provides a lightweight shim for the gnulib test framework (init.sh) with implementations of compare_, returns_, skip_, framework_failure_, and all require_* functions - Executes each .sh test script from the GNU testsuite directly, injecting our Rust sed binary via PATH - Uses a clean srcdir with symlinks to real test data files - Adds per-test timeout (10s) to catch infinite loops, with SIGTERM isolation so timeout signals don't kill the parent script - Properly propagates exit codes (0=pass, 77=skip, 99=framework failure) Results are now consistent with CI tracking (~12% pass rate) with clear PASS/FAIL/SKIP/timeout categorization. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

kevinburkesegment:fix/gnu-testsuite-harness

42 minutes ago

fix: rewrite GNU testsuite harness to run upstream test scripts directly The previous harness tried to extract sed commands from GNU test scripts via regex pattern matching, which produced false negatives (comparing against empty expected output) and false positives. This led to inflated test counts and unreliable pass/fail signals. The new approach: - Provides a lightweight shim for the gnulib test framework (init.sh) with implementations of compare_, returns_, skip_, framework_failure_, and all require_* functions - Executes each .sh test script from the GNU testsuite directly, injecting our Rust sed binary via PATH - Uses a clean srcdir with symlinks to real test data files - Adds per-test timeout (10s) to catch infinite loops, with SIGTERM isolation so timeout signals don't kill the parent script - Properly propagates exit codes (0=pass, 77=skip, 99=framework failure) Results are now consistent with CI tracking (~12% pass rate) with clear PASS/FAIL/SKIP/timeout categorization. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

kevinburkesegment:fix/gnu-testsuite-harness

1 hour ago

chore(deps): update dawidd6/action-download-artifact action to v19

main

8 hours ago

chore(deps): update dawidd6/action-download-artifact action to v19

renovate/dawidd6-action-download-artifact-19.x

9 hours ago

fix: use foreground timeout to prevent orphaned process hangs The previous approach (background process + manual watchdog) left orphaned sed processes that could block the script or cause the CI runner to kill the entire step (exit code 143). Switch to running `timeout --kill-after=5 30` in the foreground with output redirected to a file. This lets timeout properly manage the child process tree and avoids pipe-blocking issues entirely. Also detect exit code 125 (uutils timeout) in addition to 124 (GNU coreutils timeout) and 137 (SIGKILL). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

kevinburkesegment:fix/gnu-testsuite-harness

20 hours ago

fix: use file-based output for test timeout handling When a test hangs and the watchdog kills the shell, orphaned child processes (e.g. our sed binary in an infinite loop) can keep a pipe's write end open, causing the $() subshell capture to block indefinitely. Switch to writing test output to a temp file instead of capturing via pipe. This ensures the parent script always returns promptly after the watchdog fires, regardless of orphaned processes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

kevinburkesegment:fix/gnu-testsuite-harness

20 hours ago

fix: rewrite GNU testsuite harness to run upstream test scripts directly The previous harness tried to extract sed commands from GNU test scripts via regex pattern matching, which produced false negatives (comparing against empty expected output) and false positives. This led to inflated test counts and unreliable pass/fail signals. The new approach: - Provides a lightweight shim for the gnulib test framework (init.sh) with implementations of compare_, returns_, skip_, framework_failure_, and all require_* functions - Executes each .sh test script from the GNU testsuite directly, injecting our Rust sed binary via PATH - Uses a clean srcdir with symlinks to real test data files - Adds 30s timeout per test to catch infinite loops - Properly propagates exit codes (0=pass, 77=skip, 99=framework failure) Results are now consistent with CI: 65 tests, ~12% pass rate, with clear PASS/FAIL/SKIP/timeout categorization. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

kevinburkesegment:fix/gnu-testsuite-harness

22 hours ago

fix: rewrite GNU testsuite harness to run upstream test scripts directly The previous harness tried to extract sed commands from GNU test scripts via regex pattern matching, which produced false negatives (comparing against empty expected output) and false positives. This led to inflated test counts and unreliable pass/fail signals. The new approach: - Provides a lightweight shim for the gnulib test framework (init.sh) with implementations of compare_, returns_, skip_, framework_failure_, and all require_* functions - Executes each .sh test script from the GNU testsuite directly, injecting our Rust sed binary via PATH - Uses a clean srcdir with symlinks to real test data files - Adds 30s timeout per test to catch infinite loops - Properly propagates exit codes (0=pass, 77=skip, 99=framework failure) Results are now consistent with CI: 65 tests, ~12% pass rate, with clear PASS/FAIL/SKIP/timeout categorization. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

kevinburkesegment:fix/gnu-testsuite-harness

22 hours ago

Active Branches

fix: rewrite GNU testsuite harness to run upstream test scripts directly#343

last run

42 minutes ago

0%

Add support for address range commands (GNU extension)#260

last run

3 days ago

0%

Fix truncated pattern space problem#263

last run

4 days ago

0%

© 2026 CodSpeed Technology

Home Terms Privacy Docs