Created attachment 897640 [details] build.log and emerge --info 4/8 Testing: lib-numeric-formats 4/8 Test: lib-numeric-formats Command: "/var/tmp/portage/media-sound/audacity-3.4.2-r1/work/audacity-sources-3.4.2_build/tests/lib-numeric-formats-test" Directory: /var/tmp/portage/media-sound/audacity-3.4.2-r1/work/audacity-sources-3.4.2 "lib-numeric-formats" start time: Jul 14 21:33 UTC Output: ---------------------------------------------------------- 21:33:51: Debug: GetSupportedPlaybackRates() Could not get device info! 21:33:51: Debug: GetSupportedCaptureRates() Could not get device info! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ lib-numeric-formats-test is a Catch v2.13.8 host application. Run with -? for options ------------------------------------------------------------------------------- BeatsNumericConverterFormatter ------------------------------------------------------------------------------- /var/tmp/portage/media-sound/audacity-3.4.2-r1/work/audacity-sources-3.4.2/libraries/lib-numeric-formats/tests/NumericConverterTests.cpp:71 ............................................................................... /var/tmp/portage/media-sound/audacity-3.4.2-r1/work/audacity-sources-3.4.2/libraries/lib-numeric-formats/tests/NumericConverterTests.cpp:225: FAILED: REQUIRE( basicFormatter ->ValueToString( *basicFormatter->StringToValue(formattedString), true) .valueString == formattedString ) with expansion: 189 bar 01 beat == 189 bar 02 beat =============================================================================== test cases: 2 | 1 passed | 1 failed assertions: 1558 | 1557 passed | 1 failed <end of output> Test time = 0.02 sec ---------------------------------------------------------- Test Failed. "lib-numeric-formats" end time: Jul 14 21:33 UTC "lib-numeric-formats" time elapsed: 00:00:00 ----------------------------------------------------------
Does it fail anywhere else? This one feels kind of curious.
(In reply to Sam James from comment #1) > Does it fail anywhere else? This one feels kind of curious. Hmm, also fails on arm64, could have sworn I tested it on amd64 and it did not, will confirm this shortly.
So this indeed reproduces on arm64, but not on amd64.
Created attachment 897842 [details] build.log and emerge --info (riscv) Reproduces on riscv as well. So looks like, all non-x86.
What about 3.7.0 then? stabilisation in bug 945646
Created attachment 916194 [details] build.log and emerge --info This is still an issue on 3.7.0. Log from arm64.