On 2015-03-30 04:30, Tom Lee wrote: > Hey Niels, > > Understood. Hard to see exactly what's going on here because we seem to be > falling afoul of https://lists.debian.org/debian-devel/2014/04/msg00322.html. > Do you happen to know if there's another way to get access to > test-suite.log from these builds? The suggested work-around in that mailing > list thread appears to require a change to the packaging, which I imagine > we want to try and avoid. > > Cheers, > Tom > > > [...]
Hi Tom, I see no problem in adding a "VERBOSE=1" (or --disable-silent-rules, or whatever), as it does not have an effect of the produced built. In fact, I am not aware of any other way to obtain the test-suite.log from the buildds. To my knowledge, the buildds more or less discards the build environment immediately after the build terminates. My best alternative is for you to get -guest access to a porterbox and try to reproduce it there[1]. It may take some time before you get such an account. It might make sense for you to try that in parallel with the build logs - just in case the build logs are not enough for you to fix the issue. DDs also have access to porterboxes, so you might also be able to convince your sponsor to help you with obtaining additional information from the porterbox. Though, in this case, you will probably want to "stack up" a few things to save a few "roundtrips". Maybe something like: """ * Please build the package and which fail the tests * Extract test-build.log * Run the test via gdb and do a "bt" at the point it seg. faults. * Extract stacktrace from gdb and attach it along with the test-build.log * ... """ Thanks, ~Niels [1] https://dsa.debian.org/doc/guest-account/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
