Re: tests/test-suite.log build failures

2014-04-13 Thread Guillem Jover
Hi! On Sun, 2014-04-13 at 15:38:05 +0200, Xavier Roche wrote: > I had a build failure (*) on my package due to a failing unit test, and > the only information I got (with the failng unit test) was: > > # TOTAL: 12 > # PASS: 11 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > ==

Re: tests/test-suite.log build failures

2014-04-13 Thread Simon McVittie
On 13/04/14 14:38, Xavier Roche wrote: > I had a build failure (*) on my package due to a failing unit test, and > the only information I got (with the failng unit test) was: > > # TOTAL: 12 > # PASS: 11 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 This is a "feature" of rece

Re: tests/test-suite.log build failures

2014-04-13 Thread Cyril Brulebois
Xavier Roche (2014-04-13): > > See tests/test-suite.log > > Would it be relevant to emit to stderr the tests/test-suite.log content > in this case to ease debugging (or to keep it somehow) ? That's a good idea, yeah. Th

tests/test-suite.log build failures

2014-04-13 Thread Xavier Roche
Hi folks! I had a build failure (*) on my package due to a failing unit test, and the only information I got (with the failng unit test) was: # TOTAL: 12 # PASS: 11 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0