From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Antw: build speedup possible?
Date: Mon, 10 Feb 2014 09:38:47 +0100 [thread overview]
Message-ID: <20140210093847.6913b9b4@skate> (raw)
In-Reply-To: <CAHkwnC9Ayss7OYdSTbSp07LKy0GQ801TCdgxiVSNPpKew8i0OQ@mail.gmail.com>
Dear Fabio Porcedda,
On Fri, 7 Feb 2014 19:05:34 +0100, Fabio Porcedda wrote:
> > I don't really see how to reproduce the exact build order, so the
> > support problem will be here. That's really why I have been a bit
> > skeptical and resistant to this patch series from the very beginning. I
> > am obviously very interested in ways to reduce the build time. But
> > doing that at the expense of reliability is not a good idea in my
> > opinion, as users will face spurious failures that we will not be able
> > to reproduce and fix.
>
> About the spurious failures when building packages in parallel IMHO
> they depends only on the building order of the finished steps.
> If a build fails IMHO it depends on something that is not available so
> those failures can be reproduced considering only the finished steps
> and ignoring the overlapping unfinished steps.
> What do you think about that?
Of course even with parallel build it is *possible* to understand what
happened. But it is much more complicated because we cannot simply take
the user .config file, replay the build, and reproduce the issue. We
would need to have access to the user's complete build log to see in
which order things happened, and from this get an understanding of what
the issue could be. And the thing is that 99% of the time, users do not
save their build log into a file, so when they come on
IRC/bugtracker/mailing list for support, they only have the last few
lines of build output.
We're not talking about theory here, but practice. In theory, all
parallel build problems can be solved. In practice, it will make
supporting users much more complicated, as we will not be able to
reproduce their builds, and we won't have enough informations about the
order in which things happened.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-10 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 8:51 [Buildroot] build speedup possible? Andreas Naumann
2014-02-07 8:54 ` Maxime Hadjinlian
2014-02-07 9:00 ` [Buildroot] Antw: " Frank Ihle
2014-02-07 10:31 ` Samuel Martin
2014-02-07 13:35 ` Andreas Naumann
2014-02-07 15:17 ` Fabio Porcedda
2014-02-07 14:48 ` Fabio Porcedda
2014-02-07 15:03 ` Fabio Porcedda
2014-02-07 15:29 ` Thomas Petazzoni
2014-02-07 15:54 ` Fabio Porcedda
2014-02-07 16:43 ` Thomas Petazzoni
2014-02-07 18:05 ` Fabio Porcedda
2014-02-10 8:38 ` Thomas Petazzoni [this message]
2014-02-10 11:31 ` Andreas Naumann
2014-02-10 12:15 ` Thomas Petazzoni
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=20140210093847.6913b9b4@skate \
--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