Kevin Burke 16f11456b3 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>

2026-03-19 22:04:56 +01:00

..

bench-compare.sh

Report performance changes up to 1%

2025-05-25 15:16:21 +03:00

benchmark.sh

Adjust benchmark for Windown execution

2025-12-16 21:07:09 +01:00

compare_test_results.py

python coding style on the file

2026-01-28 09:32:24 +01:00

publish.sh

empty sed for reimplementation

2025-02-01 18:07:27 +01:00

run-gnu-testsuite.sh

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

2026-03-19 22:04:56 +01:00

test_compare_test_results.py

Improve comparison output to show both current and reference numbers

2026-01-11 17:12:41 +01:00