test error analysis on build services

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/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Thu Jan 26 13:29:28 UTC 2017


On Wed, Jan 25, 2017 at 01:14:40PM +0100, Holger Freyther wrote:
> 
> > On 25 Jan 2017, at 12:23, Neels Hofmeyr <nhofmeyr at sysmocom.de> wrote:
> > 
> > On jenkins and opensuse, we have builds where we cannot easily analyse the
> > testsuite.dir after a build failed. So we only see which tests failed and not
> > why.
> > 
> > On jenkins I have in most places added a script invocation that prints all
> > testsuite.dir/*/*.log in case of build failure, so we can see it in the jenkins
> > log right away.
> 
> dh_override_auto_test:
> 	make check || (cat ... && false)?
> 
> into the debian/rules or such?

(and this in all of our source trees)
Thanks!
Now someone has to still write the patches and test them...

> most likely timing... the test is using realtime... we should consider mocking
> gettimeofday in some way?

Related:
https://git.osmocom.org/libosmocore/commit/?id=8e2f7e87f4d854e697c40545326a16e50614dd5c
and its first and so far only caller
https://git.osmocom.org/libosmocore/commit/?id=7b4d727ec5debc3d057686a0a3f0f5f14260a282
from http://osmocom.org/issues/1809.

~N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170126/cccac9ee/attachment.bin>


More information about the OpenBSC mailing list