Bug#1052888: epics-base: FTBFS: make[2]: *** [configure/RULES_TOP:62: runtests] Error 1

Andrius Merkys merkys at debian.org
Tue Oct 10 07:54:01 BST 2023


Control: tags -1 + unreproducible

On Tue, 26 Sep 2023 15:34:01 +0200 Lucas Nussbaum <lucas at debian.org> wrote:
> Source: epics-base
> Version: 7.0.7+dfsg1-5
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lucas at debian.org
> Usertags: ftbfs-20230925 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

I cannot reproduce the issue on amd64. From your log the relevant part 
seems to be the following:

epicsEventTrigger: pthread_mutex_lock failed: Invalid argument
epicsEventMustTriggerThread CAC-event (0x7f4370025b30) can't proceed, 
suspending.
Dumping a stack trace of thread 'CAC-event':
[    0x7f4384e76943]: 
/<<PKGBUILDDIR>>/lib/linux-x86_64/libCom.so.3.22.0(epicsStackTrace+0x73)
[    0x7f4384e679a9]: 
/<<PKGBUILDDIR>>/lib/linux-x86_64/libCom.so.3.22.0(cantProceed+0xc9)
[    0x7f4384eec0b1]: 
/<<PKGBUILDDIR>>/lib/linux-x86_64/libdbCore.so.3.22.0(testdbCaWaitForEventCB+0x21)
[    0x7f4384b4a2bc]: 
/<<PKGBUILDDIR>>/lib/linux-x86_64/libca.so.4.14.2(_ZN15oldSubscription7currentER10epicsGuardI10epicsMutexEjmPKv+0x6c)
[    0x7f4384ef052a]: 
/<<PKGBUILDDIR>>/lib/linux-x86_64/libdbCore.so.3.22.0(_ZN9dbContext15callStateNotifyEP9dbChanneljmPK12db_field_logR14cacStateNotify+0x17a)
[    0x7f4384ee4645]: 
/<<PKGBUILDDIR>>/lib/linux-x86_64/libdbCore.so.3.22.0(event_task+0x1e5)
[    0x7f4384e70842]: 
/<<PKGBUILDDIR>>/lib/linux-x86_64/libCom.so.3.22.0(start_routine+0xd2)
[    0x7f4384cd13ec]: 
/lib/x86_64-linux-gnu/libc.so.6(pthread_condattr_setpshared+0x4cc)
[    0x7f4384d51a2c]: /lib/x86_64-linux-gnu/libc.so.6(__clone+0x11c)
Thread CAC-event (0x7f4370025b30) suspended
regressTest.t: Timed out './regressTest' after 500 seconds
regressTest.t ...........

I think the test has timed out due to the high load of the building 
machine. If this persists, increasing the timeout value could be a solution.

Cheers,
Andrius



More information about the debian-science-maintainers mailing list