[libvirt] where is config.log when debugging a failure reported by Jenkins
Hello Jenkins folks, On the libvirt list, we came across a case where a broken commit was detected, but where the information available in the failure report was insufficient (for at least me) to reproduce the failure environment without asking more questions: http://honk.sigxcpu.org:8001/job/libvirt-build/472/ https://www.redhat.com/archives/libvir-list/2013-January/msg00037.html Is there any way that things can be tweaked to include the 'config.log' file in the web report of a failed build? Merely capturing the output of './configure' fails to provide some of the details that are intentionally redirected into the more verbose config.log file. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Hi Eric, On Wed, Jan 02, 2013 at 02:45:24PM -0700, Eric Blake wrote:
Hello Jenkins folks,
On the libvirt list, we came across a case where a broken commit was detected, but where the information available in the failure report was insufficient (for at least me) to reproduce the failure environment without asking more questions: http://honk.sigxcpu.org:8001/job/libvirt-build/472/ https://www.redhat.com/archives/libvir-list/2013-January/msg00037.html
Is there any way that things can be tweaked to include the 'config.log' file in the web report of a failed build? Merely capturing the output of './configure' fails to provide some of the details that are intentionally redirected into the more verbose config.log file.
Since the build job itself is a just a shell script I can cat that file to stdout in case of failure. I've changed the job to do so. Cheers, -- Guido
-- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
On Wed, Jan 02, 2013 at 11:12:31PM +0100, Guido Günther wrote:
Hi Eric, On Wed, Jan 02, 2013 at 02:45:24PM -0700, Eric Blake wrote:
Hello Jenkins folks,
On the libvirt list, we came across a case where a broken commit was detected, but where the information available in the failure report was insufficient (for at least me) to reproduce the failure environment without asking more questions: http://honk.sigxcpu.org:8001/job/libvirt-build/472/ https://www.redhat.com/archives/libvir-list/2013-January/msg00037.html
Is there any way that things can be tweaked to include the 'config.log' file in the web report of a failed build? Merely capturing the output of './configure' fails to provide some of the details that are intentionally redirected into the more verbose config.log file.
Since the build job itself is a just a shell script I can cat that file to stdout in case of failure. I've changed the job to do so. Even better: let's collect config.log as a build artifact so we have it for all builds and don't clutter up the build log itself. -- Guido
participants (2)
-
Eric Blake -
Guido Günther