It seems to be a sporadic failure due to timing. Kicking off the same build on jenkins resulted in success. Can anyone relaunch the OBS build? I'm not too familiar with it...
http://jenkins.osmocom.org/jenkins/job/libosmo-netif/ https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/li...
Also, it would actually be nice if the opensuse builds also printed all test logs as in osmo-ci/scripts/cat-testlogs.sh -- if anyone knows how and has the time to insert such, that would be great.
(git clone https://gerrit.osmocom.org/osmo-ci)
Thanks, ~N
On 28 Feb 2017, at 19:27, Neels Hofmeyr nhofmeyr@sysmocom.de wrote:
It seems to be a sporadic failure due to timing. Kicking off the same build on jenkins resulted in success. Can anyone relaunch the OBS build? I'm not too familiar with it...
http://jenkins.osmocom.org/jenkins/job/libosmo-netif/ https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/li...
done. If you are logged in and open the above page you can see "Start refresh", "Download logfile" and "Rebuild"
Also, it would actually be nice if the opensuse builds also printed all test logs as in osmo-ci/scripts/cat-testlogs.sh -- if anyone knows how and has the time to insert such, that would be great.
(git clone https://gerrit.osmocom.org/osmo-ci)
@ruben: Is there something to do that easily? Is there a dedicated make rule that is called after (test) failure? Would you know of a snippet for dh_override_auto_test to use? dh_autotest || dump_logs and let it fail?
holger
-
Holger Freyther -
Neels Hofmeyr