From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] New autobuild.b.o feature: build duration
Date: Sat, 3 Dec 2016 15:41:28 +0100 [thread overview]
Message-ID: <20161203154128.35314298@free-electrons.com> (raw)
Hello,
After having recently added the C library, sub-architecture and static
vs. dynamic information to autobuild.b.o, I've added today yet another
column: the build duration.
For me, the key advantage of this column is to be able to more easily
identify one of the shortest build (in duration) that allows to
reproduce a given autobuilder failure.
Of course, the duration information is a bit relative, as it depends on
the speed of the autobuilder machine on which the build took place. But
it should give some rough idea of whether a very long build was needed
before reaching the failure or not.
Hopefully this will be useful for others as well.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
reply other threads:[~2016-12-03 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161203154128.35314298@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox