big-endian s390x: polygonToCells_reported.fuzzer_crash: t_assert failed at ./src/apps/testapps/testPolygonToCellsReportedExperimental.c:54, sz == 1, Expected output count
The Debian package build for 4.2.0 fails on the big-endian s390x architecture:
12:28:01 test 101
12:28:01 Start 101: testPolygonToCellsReportedExperimental_test101
12:28:01
12:28:01 101: Test command: /<<PKGBUILDDIR>>/obj-s390x-linux-gnu/bin/testPolygonToCellsReportedExperimental
12:28:01 101: Working Directory: /<<PKGBUILDDIR>>/obj-s390x-linux-gnu
12:28:01 101: Test timeout computed to be: 1500
12:28:01 101: polygonToCells_reported.fuzzer_crash: t_assert failed at ./src/apps/testapps/testPolygonToCellsReportedExperimental.c:54, sz == 1, Expected output count
12:28:01 101: TEST polygonToCells_reported
12:28:01 101/280 Test #101: testPolygonToCellsReportedExperimental_test101 ...***Failed 0.12 sec
12:28:01 polygonToCells_reported.fuzzer_crash: t_assert failed at ./src/apps/testapps/testPolygonToCellsReportedExperimental.c:54, sz == 1, Expected output count
12:28:01 TEST polygonToCells_reported
Full build log: https://jengus.postgresql.org/job/libh3-binaries/10/architecture=s390x,distribution=sid/console
This is the only test that is failing in this version. On 4.1.0, the tests were succeeding.
Is this running on a real s390x machine or virtualized? Do you have instructions for running the tests on this architecture for debugging?
This test case came directly from a fuzzer, which is probably why it is not reproducing cleanly on other architectures. We can loosen the test assertions, remove the test, or try to rewrite the test.
It's an actual s390x machine, hosted at https://linuxone.cloud.marist.edu/. I guess you could get an account there to spin up a test machine.
Good point about the fuzzer, I'll see if I can disable the test here.