Osmocom Libraries » libosmocore

I'm looking into the current series of OBS failures. Failures on x86_64 and i568 are sporadic timeout or i/o errors in OBS that we can't do much about.

For armv7l debian9, there are two failing packages:

• libosmocore: exec_test is failing
• osmo-usecups: 'implicit declaration of function 'osmo_signalfd_setup'
  • probably a follow-up error of the outdated libosmocore

Details about the libosmocore error:

The check was introduced in: https://gerrit.osmocom.org/c/libosmocore/+/16619

For some reason, the 'env | grep MAHLZEIT 1>&2' command produces an empty stderr on that system instead of "MAHLZEIT=spaet". (The test sets the environment variable first.)

However, the patch has been merged in December, and this error has only started to show up in OBS builds on 2020-04-19.

https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/libosmocore/Debian_9.0/armv7l

...
[  887s] ## ---------------------- ##
[  887s] ## Detailed failed tests. ##
[  887s] ## ---------------------- ##
[  887s] 
[  887s] #                             -*- compilation -*-
[  887s] 59. testsuite.at:372: testing exec ...
[  887s] ./testsuite.at:376: $abs_top_builddir/tests/exec/exec_test
[  887s] --- experr    2020-05-04 01:46:19.740000000 +0000
[  887s] +++ /usr/src/packages/BUILD/tests/testsuite.dir/at-groups/59/stderr    2020-05-04 01:46:19.740000000 +0000
[  887s] @@ -1 +0,0 @@
[  887s] -MAHLZEIT=spaet
[  887s] 59. testsuite.at:372: 59. exec (testsuite.at:372): FAILED (testsuite.at:376)
[  887s] 
[  887s] 
[  887s] ## ------------- ##
[  887s] ## ../config.log ##
[  887s] ## ------------- ##
...