bug-gnulib
[Top][All Lists]
Advanced

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

RFE: autobuild improvements


From: Eric Blake
Subject: RFE: autobuild improvements
Date: Wed, 02 Jan 2013 11:51:23 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0

Would it make sense to improve m4/autobuild.m4 to output a bit more
information?  For example, I just received a bug report of an automated
build failure[1,2] managed by the Jenkins autobuilder[3], but while that
particular setup captures the terminal output of './configure', it did
not point me to any 'config.log' information, so while I was able to
learn (from AC_CANONICAL_BUILD) that the host encountering the failure
was i686-pc-linux-gnu, I didn't get to find out anything about which
distro it was using, or which gcc version, glibc version, the git hash
of libvirt.git that was being built, or anything else that would help me
reproduce the bug easier.  Obviously, it would be nicer for Jenkins to
report more details on a failed build, but I'm attempting to attack this
from multiple fronts by asking whether putting more information in
actual configure output makes sense.

Autoconf already has portable code for putting lots of useful platform
information in the head of config.log (via the AS_UNAME macro), and it
might be worth repeating some of that information in actual configure
output, precisely because some people only log configure output rather
than hanging on to full config.log.

[1]http://honk.sigxcpu.org:8001/job/libvirt-build/472/
[2]https://www.redhat.com/archives/libvir-list/2013-January/msg00037.html
[3]http://jenkins-ci.org/

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]