freebsd and jenkins

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Holger Freyther holger at freyther.de
Mon Jul 4 14:11:38 UTC 2016


> On 04 Jul 2016, at 15:40, Max <msuraev at 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_amd64/101/console
> 
> 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_amd64/ws/


More information about the OpenBSC mailing list