4 Jul
2016
4 Jul
'16
4:53 p.m.
Thanks for the link. My buils is last one (#101) but there's no
testsuite.log in workspace although in console output it ways that
"testsuite.log was created." Any ideas what happened to it?
On 07/04/2016 04:11 PM, Holger Freyther wrote:
--
Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
On 04 Jul
2016, at 15:40, Max <msuraev(a)sysmocom.de> wrote:
Hi.
Hi!
Yet again I've hit an issue with jenkins
build failing on freebsd only:
http://jenkins.osmocom.org/jenkins/job/libosmocore-gerrit/label=FreeBSD_amd…
No warnings, no errors, just a failure which I'm unable to reproduce
locally as I do not have access to any machine with freebsd. If we can't
make freebsd tests optional (which I personally would prefer) can we at
least configure jenkins in a way that it runs "cat tests/testsuite.log"
so it's available via "console output" part of jenkins web ui? Or
somehow else provide access to build artifacts. That will give at least
some clue as to what exactly is broken on freebsd.
a.) We/you add the cat to contrib/jenkins.sh
b.) if your build is the last one, you can (after you logged in) inspect the
workspace[1]. My internet is too slow right now to look for the specific entry.
holger
[1] http://jenkins.osmocom.org/jenkins/job/libosmocore-gerrit/label=FreeBSD_amd…