> On 25 Jan 2017, at 12:23, Neels Hofmeyr <[email protected]> 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?
> My main goal right now is to see why/how the libosmo-netif OBS build failed
> (osmux test fails) without further local reproduction effort. This situation
> will certainly repeat over and over, for all of the other projects as well.
most likely timing... the test is using realtime... we should consider mocking
gettimeofday in some way?
holger
