hello,
when trying to package 3.2.0 on gentoo linux, i encountered some issues during the test phase. full log is in the attachment:
Test phase: media-libs/rubberband-3.2.0
MALLOC_PERTURB_=7 /var/tmp/portage/media-libs/rubberband-3.2.0/work/rubberband-3.2.0-abi_x86_32.x86/tests --run_test=TestStretcher --log_level=message ――――――――――――――――――――――――――――――――――――― ✀
――――――――――――――――――――――――――――――――――――― stdout: Running 69 test cases... ../rubberband-3.2.0/src/test/TestStretcher.cpp(422): error: in "TestStretcher/sinusoid_slow_higher_realtime_finer": check expected - rms < maxUnder has failed [0.70710678118654757 - 0.58194117738335283 >= 0.10000000000000001] ../rubberband-3.2.0/src/test/TestStretcher.cpp(422): error: in "TestStretcher/sinusoid_fast_higher_realtime_finer": check expected - rms < maxUnder has failed [0.70710678118654757 - 0.58239831167261791 >= 0.10000000000000001] ../rubberband-3.2.0/src/test/TestStretcher.cpp(401): error: in "TestStretcher/sinusoid_fast_higher_realtime_finer_hqpitch": check positiveCrossings >= expectedCrossings - slack has failed [25 < 29] ../rubberband-3.2.0/src/test/TestStretcher.cpp(401): error: in "TestStretcher/sinusoid_fast_higher_realtime_finer_hcpitch": check positiveCrossings >= expectedCrossings - slack has failed [25 < 29] ../rubberband-3.2.0/src/test/TestStretcher.cpp(400): error: in "TestStretcher/sinusoid_slow_lower_realtime_finer_hqpitch": check positiveCrossings <= expectedCrossings + slack has failed [82 > 81] ../rubberband-3.2.0/src/test/TestStretcher.cpp(422): error: in "TestStretcher/sinusoid_slow_lower_realtime_faster_hqpitch": check expected - rms < maxUnder has failed [0.70710678118654757 - 0.505255378738942 >= 0.20000000000000001] ../rubberband-3.2.0/src/test/TestStretcher.cpp(747): error: in "TestStretcher/impulses_2x_offline_faster": check peak1 < n + 50 has failed [10446 >= 10050] ../rubberband-3.2.0/src/test/TestStretcher.cpp(951): error: in "TestStretcher/impulses_slow_lower_realtime_finer": check peak1 > int(ceil(4840 * timeRatio)) has failed [38415 <= 38720] ../rubberband-3.2.0/src/test/TestStretcher.cpp(951): error: in "TestStretcher/impulses_slow_lower_realtime_finer_hcpitch": check peak1 int(ceil(4840 * timeRatio)) has failed [38415 <= 38720] ../rubberband-3.2.0/src/test/TestStretcher.cpp(1122): error: in "TestStretcher/final_fast_samepitch_realtime_finer": check outcount >= nOut has failed [384 < 2000] ../rubberband-3.2.0/src/test/TestStretcher.cpp(1122): error: in "TestStretcher/final_fast_samepitch_realtime_finer_after": check outcount >= nOut has failed [384 < 2000] ../rubberband-3.2.0/src/test/TestStretcher.cpp(1122): error: in "TestStretcher/final_fast_higher_realtime_finer": check outcount >= nOut has failed [1108 < 2000] ../rubberband-3.2.0/src/test/TestStretcher.cpp(1122): error: in "TestStretcher/final_fast_higher_realtime_finer_after": check outcount = nOut has failed [1108 < 2000] ../rubberband-3.2.0/src/test/TestStretcher.cpp(1122): error: in "TestStretcher/final_fast_lower_realtime_finer": check outcount >= nOut has failed [0 < 2000] ../rubberband-3.2.0/src/test/TestStretcher.cpp(1122): error: in "TestStretcher/final_fast_lower_realtime_finer_after": check outcount >= nOut has failed [0 < 2000] stderr:
*** 15 failures are detected in the test module "RubberBand"
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
Summary of Failures:
8/8 Stretcher FAIL 9.59s (exit status 201 or signal 73 SIGinvalid)
Ok: 7 Expected Fail: 0 Fail: 1 Unexpected Pass: 0 Skipped: 0 Timeout: 0
abi_x86_32.x86
This is a 32-bit build?
(A 32-bit build should work of course, but that would explain why there might be differences and why I might not have noticed them!)
the ebuild can build both 64-bit and 32-bit versions of the library. this failure is on 32-bit library. as it failed these tests, it did not test the 64-bit one.
It turned out the tests failed in any build using resamplers other than the built-in one (see also https://github.com/breakfastquay/rubberband/issues/83 ). However there was a further failure specific to 32-bit builds as well!
Those are now fixed - I hope! - in today's 3.2.1 release.