On 23/10/14 22:43, intrigeri wrote: > Hi, > > Ximin Luo wrote (14 Oct 2014 11:59:20 GMT) : >> On 13/10/14 18:08, David Suárez wrote: >>>> See ./test-suite.log >> Do you have access to this file? Can you send it here? > > (The following assumes that the upstream or Debian packaging is > responsible for sending the detailed test suite output to > test-suite.log; if I'm wrong, please ask me to look closer.) > > I doubt David keeps all build trees around for archive rebuilds, but > who knows. > > Anyway: one of these days, such a FTBFS caused by a test suite failure > will happen on a buildd, and then you'll have the same problem for > debugging, and will be asking the same question to some buildd admin, > and likely the answer will be "no, sorry". > > For this reason, IMO any useful output generated when building this > package should go to stdout and stderr, including the test suite > one, probably. >
OK, I will try to reproduce this when I get some time. FWIW, test-suite.log is from automake tests, so it is fairly standard... but I'll see if I can configure it to dump to stderr. It may not be trivial though, because the invocation is something to the effect of "make test-suite.log", and putting it to stderr would break that pattern. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
