Source: epics-base
Version: 7.0.8+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramacher@debian.org

https://buildd.debian.org/status/fetch.php?pkg=epics-base&arch=amd64&ver=7.0.8%2Bdfsg1-1&stamp=1709732504&raw=0

make[6]: Nothing to be done for 'runtests'.
make[6]: Leaving directory '/<<PKGBUILDDIR>>/modules/pva2pva/iocBoot/iocwfdemo' make[5]: Leaving directory '/<<PKGBUILDDIR>>/modules/pva2pva/iocBoot'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/modules/pva2pva'
make[3]: Leaving directory '/<<PKGBUILDDIR>>/modules'

Tests failed in:
/<<PKGBUILDDIR>>/modules/pvAccess/testApp/O.linux-x86_64
/<<PKGBUILDDIR>>/modules/pvDatabase/test/O.linux-x86_64
make[2]: *** [configure/RULES_TOP:62: runtests] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [debian/rules:31: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:22: build-arch] Error 2

Cheers
--
Sebastian Ramacher

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Here an analyse of the FTBFS

On the amd64, I have two failures dureing the test

Test Summary Report
-------------------
testPVAServer.t (Wstat: 0 Tests: 0 Failed: 0)
Parse errors: No plan found in TAP output
Files=6, Tests=129, 1 wallclock secs ( 0.05 usr 0.01 sys + 0.09 cusr 0.06 csys = 0.21 CPU)
Result: FAIL
-------------------

and

Test Summary Report
-------------------
testInetAddressUtils.t (Wstat: 0 Tests: 65 Failed: 0)
TODO passed: 64
testChannelAccess.t (Wstat: 0 Tests: 152 Failed: 0)
TODO passed: 45
testServerContext.t (Wstat: 0 Tests: 0 Failed: 0)
Parse errors: No plan found in TAP output
Files=12, Tests=6381, 27 wallclock secs ( 0.38 usr 0.03 sys + 0.42 cusr 0.18 csys = 1.01 CPU)
Result: FAIL
-------------------

on arm64, the first test seems to work...

testPVAServer.t ......
1..1
pvAccess Server v7.1.7
Active configuration (w/ defaults)
EPICS_PVAS_INTF_ADDR_LIST = 0.0.0.0:5075
EPICS_PVAS_BEACON_ADDR_LIST =
EPICS_PVAS_AUTO_BEACON_ADDR_LIST = YES
EPICS_PVAS_BEACON_PERIOD = 15
EPICS_PVAS_BROADCAST_PORT = 5076
EPICS_PVAS_SERVER_PORT = 5075
EPICS_PVAS_PROVIDER_NAMES = local
ok 1 - ctx.get()!=0
ok

I am wondering if this is not something related to the network configuration.


i386

Test Summary Report
-------------------
printfTest.t (Wstat: 256 (exited 1) Tests: 97 Failed: 1)
Failed test: 70
Non-zero exit status: 1
Files=22, Tests=5033, 29 wallclock secs ( 0.42 usr 0.04 sys + 1.74 cusr 0.34 csys = 2.54 CPU)
Result: FAIL
-------------------

Test Summary Report
-------------------
testInetAddressUtils.t (Wstat: 0 Tests: 65 Failed: 0)
TODO passed: 64
testChannelAccess.t (Wstat: 0 Tests: 152 Failed: 0)
TODO passed: 45
testServerContext.t (Wstat: 0 Tests: 0 Failed: 0)
Parse errors: No plan found in TAP output
Files=12, Tests=6381, 26 wallclock secs ( 0.42 usr 0.02 sys + 0.46 cusr 0.20 csys = 1.10 CPU)
Result: FAIL
-------------------

Test Summary Report
-------------------
testPVAServer.t (Wstat: 0 Tests: 0 Failed: 0)
Parse errors: No plan found in TAP output
Files=6, Tests=129, 0 wallclock secs ( 0.08 usr 0.02 sys + 0.10 cusr 0.04 csys = 0.24 CPU)
Result: FAIL
-------------------


And there is a bunch of unsupported architectures.

/<<PKGBUILDDIR>>/src/tools/EpicsHostArch.pl: Architecture 'mips64el-linux-gnuabi64-thread-multi' not recognized

/<<PKGBUILDDIR>>/src/tools/EpicsHostArch.pl: Architecture 'powerpc64le-linux-gnu-thread-multi' not recognized

/<<PKGBUILDDIR>>/src/tools/EpicsHostArch.pl: Architecture 'riscv64-linux-gnu-thread-multi' not recognized

/<<PKGBUILDDIR>>/src/tools/EpicsHostArch.pl: Architecture 's390x-linux-gnu-thread-multi' not recognized

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)