where is config.log when debugging a failure reported by Jenkins

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

Attachment: signature.asc
Description: OpenPGP digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]