On Wed, Jan 23, 2008 at 17:19:15 -0500, Michael Stone wrote: > On Wed, Jan 23, 2008 at 11:11:23PM +0100, Luk Claes wrote: >> Do you even care looking at the build logs or do you really want to be >> pointed at them? They are available as usual on buildd.debian.org... > > Sorry, I meant "test log" rather than "build log". The details about why > the test failed are left in a file in the build directory. The build log > tells what failed, but doesn't display the debug information that would > explain why. Normally one could duplicate the problem with a manual > build, but that's not happening this time. (The manual build passes that > step, and runs into the other problem with the wacky unexpected error > codes later in the test sequence.) > Maybe you could modify the build rules to cat the test logs in case of failure?
Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
