Bug#903612: csound FTBFS on !x86: test hang

[Adrian Bunk]

Source: csound
Version: 1:6.11.0~dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=csound&suite=sid
(m68k is building with nocheck)

...
debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
OPCODE6DIR64=obj-aarch64-linux-gnu dh_auto_test
cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=3 ninja test
[0/1] Running tests...
Test project /<<PKGBUILDDIR>>/obj-aarch64-linux-gnu
Start 1: testCsoundTypeSystem
1/12 Test #1: testCsoundTypeSystem ............. Passed 0.27 sec
Start 2: testCsoundMessageBuffer
2/12 Test #2: testCsoundMessageBuffer .......... Passed 0.09 sec
Start 3: testCsoundOrcSemantics
3/12 Test #3: testCsoundOrcSemantics ........... Passed 0.29 sec
Start 4: testCsoundOrcCompileTest
4/12 Test #4: testCsoundOrcCompileTest ......... Passed 5.05 sec
Start 5: testChannels
5/12 Test #5: testChannels ..................... Passed 0.33 sec
Start 6: testCsoundDataStructures
6/12 Test #6: testCsoundDataStructures ......... Passed 0.03 sec
Start 7: testIo
7/12 Test #7: testIo ........................... Passed 0.73 sec
Start 8: testCircularBuffer
8/12 Test #8: testCircularBuffer ............... Passed 0.03 sec
Start 9: testPerfThread
9/12 Test #9: testPerfThread ................... Passed 13.07 sec
Start 10: testDebugger
10/12 Test #10: testDebugger ..................... Passed 0.09 sec
Start 11: testEngine
E: Build killed with signal TERM after 150 minutes of inactivity

[Debian Bug Tracking System]

tag -1 pending

Bug #903612 [src:csound] csound FTBFS on !x86: test hang
Added tag(s) pending.

[Debian Bug Tracking System]

Your message dated Thu, 23 Aug 2018 13:05:34 +0000
with message-id <E1fspIs-0001Yf-***@fasolo.debian.org>
and subject line Bug#903612: fixed in csound 1:6.11.0~dfsg-2
has caused the Debian Bug report #903612,
regarding csound FTBFS on !x86: test hang
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)

[Felipe Sateler]

Control: reopen -1
Control: found -1 1:6.11.0~dfsg-2
Control: retitle -1 csound: tests hang when atomic builtins are unavailable

On Thu, Aug 23, 2018 at 10:09 AM Debian Bug Tracking System <

* Unconditionally enable atomic builtins.
It was disabled in !x86 a long time ago for unclear reasons.
The lack of atomics causes a test exercising the async features to
hang
(Closes: #903612)

Turns out mips and mipsel do not support the atomic builtins used by csound.

Reopening the bug until a new solution is found.

[Debian Bug Tracking System]

Post by Felipe Sateler
reopen -1

Bug #903612 {Done: Felipe Sateler <***@debian.org>} [src:csound] csound FTBFS on !x86: test hang
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions csound/1:6.11.0~dfsg-2.

Post by Felipe Sateler
found -1 1:6.11.0~dfsg-2

Bug #903612 [src:csound] csound FTBFS on !x86: test hang
Marked as found in versions csound/1:6.11.0~dfsg-2.

Post by Felipe Sateler
retitle -1 csound: tests hang when atomic builtins are unavailable

Bug #903612 [src:csound] csound FTBFS on !x86: test hang
Changed Bug title to 'csound: tests hang when atomic builtins are unavailable' from 'csound FTBFS on !x86: test hang'.

[Debian Bug Tracking System]

tag -1 pending

Bug #903612 [src:csound] csound: tests hang when atomic builtins are unavailable
Added tag(s) pending.

[Debian Bug Tracking System]

Your message dated Fri, 07 Sep 2018 13:34:01 +0000
with message-id <E1fyGtd-0002LI-***@fasolo.debian.org>
and subject line Bug#903612: fixed in csound 1:6.11.0~dfsg-3
has caused the Debian Bug report #903612,
regarding csound: tests hang when atomic builtins are unavailable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)