From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] WIP: Test version of buildman - U-Boot builder
Date: Thu, 01 Nov 2012 00:37:25 +0100 [thread overview]
Message-ID: <20121031233725.811002005BD@gemini.denx.de> (raw)
In-Reply-To: <CAPnjgZ1qV=Odn93NMWEeAOzOOeBHyWwXB21s+n+cXXh0nan=eg@mail.gmail.com>
Dear Simon,
In message <CAPnjgZ1qV=Odn93NMWEeAOzOOeBHyWwXB21s+n+cXXh0nan=eg@mail.gmail.com> you wrote:
>
> Yes...it's mostly for building a list of commits (e.g. an entire
> branch) and automatically tracking and showing what boards break
> between commits. It is optimised for this - e.g. it can build 22
> commits for 1000 boards (22,000 builds) in about an hour on a fast
> machine, which is a few times faster than I have managed with MAKEALL.
Do you have an explanation why this is so? There must be some
fundamental difference, and I would really like to understand that.
> It is a completely different tool, yes, but I have found myself using
> it instead of what I previously used: MAKEALL plus Mike's 'buildall'
> wrapper. The main thing I like about it is that it quickly shows me
> which builds are broken by which commits, and what the errors were.
>
> I have posted it since it's not a lot of use having it privately - it
> might be useful to others.
Pleasae don;t misunderstand me. I really appreciate your posting.
And if this tool is really that fast, I want to have it, and the
sooner the better. But then, we should dump MAKEALL, especially if
it's so slow.
In the end, there should be just one such tool...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"If you can, help others. If you can't, at least don't hurt others."
- the Dalai Lama
next prev parent reply other threads:[~2012-10-31 23:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 21:25 [U-Boot] [PATCH 1/2] WIP: Changes to patman libraries Simon Glass
2012-10-31 21:25 ` [U-Boot] [PATCH 2/2] WIP: Test version of buildman - U-Boot builder Simon Glass
2012-10-31 22:46 ` Wolfgang Denk
2012-10-31 22:51 ` Tom Rini
2012-10-31 23:08 ` Simon Glass
2012-10-31 23:37 ` Wolfgang Denk [this message]
2012-11-01 0:11 ` Simon Glass
2012-11-01 1:18 ` Tom Rini
2012-11-01 4:17 ` Andy Fleming
2012-11-01 21:01 ` Simon Glass
2012-11-01 23:29 ` Tom Rini
2012-12-01 20:55 ` Simon Glass
2012-10-31 22:42 ` [U-Boot] [PATCH 1/2] WIP: Changes to patman libraries Wolfgang Denk
2012-10-31 23:12 ` Simon Glass
2012-10-31 23:40 ` Wolfgang Denk
2012-11-01 0:04 ` Simon Glass
2012-11-01 20:59 ` Simon Glass
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=20121031233725.811002005BD@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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