tests/playTests.sh | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 use bash for test script portablitity

zlibWrapper/Makefile | 10 5 + 5 - 0 !
zlibWrapper/examples/example.c | 2 1 + 1 - 0 !
2 files changed, 6 insertions(+), 6 deletions(-)

 do not build zlibwrapper examples against embedded code copies.

tests/playTests.sh | 20 15 + 5 - 0 !
1 file changed, 15 insertions(+), 5 deletions(-)

 skip memory heavy tests causing ftbfs on mips(el) and hurd buildds

contrib/pzstd/Options.cpp | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 make the build reproducible

tests/playTests.sh | 21 13 + 8 - 0 !
1 file changed, 13 insertions(+), 8 deletions(-)

 skip test failing on gnu/hurd when writing on /dev/zero or

programs/util.c | 6 4 + 2 - 0 !
1 file changed, 4 insertions(+), 2 deletions(-)

 fix ftbfs on alpha, see #962676

programs/util.c | 6 4 + 2 - 0 !
1 file changed, 4 insertions(+), 2 deletions(-)

 fix the build on kfreebsd - no utime_now.

tests/cli-tests/compression/basic.sh | 6 4 + 2 - 0 !
tests/cli-tests/compression/gzip-compat.sh | 14 8 + 6 - 0 !
tests/cli-tests/compression/window-resize.sh | 2 1 + 1 - 0 !
3 files changed, 13 insertions(+), 9 deletions(-)

 fix cli-tests issues

lib/compress/zstd_compress.c | 3 2 + 1 - 0 !
tests/cli-tests/compression/golden.sh | 4 4 + 0 - 0 !
tests/fuzzer.c | 67 67 + 0 - 0 !
tests/golden-compression/PR-3517-block-splitter-corruption-test | 1 1 + 0 - 0 !
4 files changed, 74 insertions(+), 1 deletion(-)

 fix rare corruption bug affecting the block splitter
 The block splitter confuses sequences with literal length == 65536 that use a
 repeat offset code. It interprets this as literal length == 0 when deciding the
 meaning of the repeat offset, and corrupts the repeat offset history. This is
 benign, merely causing suboptimal compression performance, if the confused
 history is flushed before the end of the block, e.g. if there are 3 consecutive
 non-repeat code sequences after the mistake. It also is only triggered if the
 block splitter decided to split the block.
 .
 All that to say: This is a rare bug, and requires quite a few conditions to
 trigger. However, the good news is that if you have a way to validate that the
 decompressed data is correct, e.g. you've enabled zstd's checksum or have a
 checksum elsewhere, the original data is very likely recoverable. So if you were
 affected by this bug please reach out.
 .
 The fix is to remind the block splitter that the literal length is actually 64K.
 The test case is a bit tricky to set up, but I've managed to reproduce the issue.

tests/cli-tests/run.py | 20 6 + 14 - 0 !
1 file changed, 6 insertions(+), 14 deletions(-)

 fix splitting test output into newlines

tests/cli-tests/run.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 raise the timeout for test commands to 10 minutes
 Some of the tests, e.g. the window-resize one, may take a long time on
 busy builder hosts.
Bug-Debian: https://bugs.debian.org/1032592