Actions
Bug #2561
closedosmo-mgw OBS nightly builds failing for 3 consecutive days
Start date:
10/09/2017
Due date:
% Done:
100%
Spec Reference:
Description
I've been receiving OBS build failure notifications like this for about 3 days, so I think since friday:
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nitb-split:nightly/osmo-mgw/xUbuntu_16.0 4/x86_64 Package network:osmocom:nitb-split:nightly/osmo-mgw failed to build in xUbuntu_16.04/x86_64 Check out the package for editing: osc checkout network:osmocom:nitb-split:nightly osmo-mgw Last lines of build log: [ 108s] [ 108s] Makefile:693: recipe for target 'check-local' failed [ 108s] make[5]: *** [check-local] Error 1 [ 108s] make[5]: Leaving directory '/usr/src/packages/BUILD/tests' [ 108s] Makefile:546: recipe for target 'check-am' failed [ 108s] make[4]: *** [check-am] Error 2 [ 108s] make[4]: Leaving directory '/usr/src/packages/BUILD/tests' [ 108s] Makefile:398: recipe for target 'check-recursive' failed [ 108s] make[3]: *** [check-recursive] Error 1 [ 108s] make[3]: Leaving directory '/usr/src/packages/BUILD/tests' [ 108s] Makefile:506: recipe for target 'check-recursive' failed [ 108s] make[2]: *** [check-recursive] Error 1 [ 108s] make[2]: Leaving directory '/usr/src/packages/BUILD' [ 108s] Makefile:797: recipe for target 'check' failed [ 108s] make[1]: *** [check] Error 2 [ 108s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 108s] dh_auto_test: make -j1 check returned exit code 2 [ 108s] debian/rules:17: recipe for target 'build' failed [ 108s] make: *** [build] Error 2 [ 108s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 108s] [ 108s] lamb68 failed "build osmo-mgw_1.0.2.20171009.dsc" at Mon Oct 9 02:58:31 UTC 2017. [ 108s] [ 108s] ### VM INTERACTION START ### [ 111s] [ 103.628587] reboot: Power down [ 111s] ### VM INTERACTION END ### [ 111s] [ 111s] lamb68 failed "build osmo-mgw_1.0.2.20171009.dsc" at Mon Oct 9 02:58:34 UTC 2017. [ 111s]
The builds fail consistently on all architectures, so we must have introduced some regression there. I'm assigning it to neels, as he has committed/pushed the most recent changes that co-incide with the time of failure. Please investigate (feel free to reassign in the sysmocom team, if you think somebody else is better suited to fix it), thanks!
Files
Actions