Hi, First of all, thanks a lot for all your work on porting Debian to the IBM z* systems! Are there any differences in the hardware or software configuration of the zandonai and zani Debian buildd hosts? There is a build-time test for the libzstd package that failed the only time when a 1.5.0 version of the package was built on the zani host, but it built successfully on the zandonai one. There were no significant differences between the four uploads of libzstd-1.5.0 - the changes that were made should have prevented a full-on FTBFS if they were applicable to the compiler/libc at all. https://buildd.debian.org/status/logs.php?pkg=libzstd&arch=s390x If somebody wants to reproduce this particular problem, I'm attaching a patch that only runs the thread pool test. Something interesting in the libzstd source: this test is specifically not run when libzstd is being cross-built using qemu. To be completely honest, I myself do not fully understand exactly what the test is supposed to do, but I wonder if the reason they don't run it when using qemu is that it might be influenced by the number of execution units (CPUs, cores, virtual cores, etc) that the build processes are allowed to use. Thanks in advance for your time, and keep up the great work! G'luck, Peter -- Peter Pentchev roam@ringlet.net roam@debian.org pp@storpool.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
--- a/tests/Makefile +++ b/tests/Makefile @@ -297,7 +297,7 @@ fuzztest: test-fuzzer test-zstream test-decodecorpus .PHONY: test -test: test-zstd test-fullbench test-fuzzer test-zstream test-invalidDictionaries test-legacy test-decodecorpus +# test: test-zstd test-fullbench test-fuzzer test-zstream test-invalidDictionaries test-legacy test-decodecorpus ifeq ($(QEMU_SYS),) test: test-pool endif
Attachment:
signature.asc
Description: PGP signature