All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fwd: Parallel build is broken
Date: Tue, 4 Sep 2018 14:00:28 -0400	[thread overview]
Message-ID: <20180904180028.GS26633@bill-the-cat> (raw)
In-Reply-To: <CAHp75VcCWEacw+fNi0_D6npuFPyUH7wF5NfongnLfvm+ruD9cg@mail.gmail.com>

On Tue, Sep 04, 2018 at 07:33:10PM +0300, Andy Shevchenko wrote:
> On Tue, Sep 4, 2018 at 6:47 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> >
> > On Tue, Sep 4, 2018 at 6:14 PM Tom Rini <trini@konsulko.com> wrote:
> > > On Tue, Sep 04, 2018 at 05:50:33PM +0300, Andy Shevchenko wrote:
> > > > On Tue, Sep 4, 2018 at 5:00 PM Tom Rini <trini@konsulko.com> wrote:
> > > > > On Tue, Sep 04, 2018 at 03:42:05PM +0300, Andy Shevchenko wrote:
> >
> > > > make clean && make edison_defconfig && make -j16
> > > >
> > > > gcc (Debian 8.2.0-4) 8.2.0
> > > > Copyright (C) 2018 Free Software Foundation, Inc.
> > > > This is free software; see the source for copying conditions.  There is NO
> > > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> > >
> > > I assume this is on Debian/unstable?
> >
> > testing
> >
> > >  I can't directly replicate this on
> > > my 24core (Debian/stretch) or 16core(Ubuntu/xenial) machines.  I'll
> > > setup a chroot soon, but since you've said -j64 is fine there too I
> > > suspect you have more cores than I.  This may be something you have to
> > > bisect for us if I can't replicate it myself.  Can you confirm how many
> > > cores you have?  I might be able to spin something up in Google compute.
> >
> > $ sed -n -e '/cpu cores/ { p; q }' /proc/cpuinfo
> > cpu cores       : 22
> 
> Did few runs (~6) on this machine with -j4, no failures so far.
> Reruning same with -j16 brings failure on ~2-3 iteration.
> 
> It seems the scope can be narrowed to:
> - many cores build system, and
> - Debian testing/unstable toolchain, and/or
> - U-Boot build system

I'm pretty sure it's a dependency problem somewhere.  Since this was
working reliably for you recently (right?) and I can't reproduce it and
you can, if you can run a git bisect to figure out what commit is
breaking things, that would be very helpful.  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180904/536b5efa/attachment.sig>

  reply	other threads:[~2018-09-04 18:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHp75Vf7XQARyuWSt7k4=K7jYXUnBo22_YJUoASUOD2iBq6dFA@mail.gmail.com>
2018-09-04 12:42 ` [U-Boot] Fwd: Parallel build is broken Andy Shevchenko
2018-09-04 14:00   ` Tom Rini
2018-09-04 14:50     ` Andy Shevchenko
2018-09-04 14:54       ` Andy Shevchenko
2018-09-04 15:03         ` Andy Shevchenko
2018-09-04 15:12           ` Andy Shevchenko
2018-09-05  8:45         ` Alex Kiernan
2018-09-05 11:57           ` Adam Ford
2018-09-05 17:31             ` Andy Shevchenko
2018-09-10 18:46             ` Trent Piepho
2018-09-12  3:01               ` Max Filippov
2018-09-04 15:14       ` Tom Rini
2018-09-04 15:47         ` Andy Shevchenko
2018-09-04 16:33           ` Andy Shevchenko
2018-09-04 18:00             ` Tom Rini [this message]
2018-09-04 18:05               ` Andy Shevchenko
2018-09-04 21:43                 ` Tom Rini
2018-09-05  4:08                   ` Bin Meng
2018-09-05  7:22                   ` Joakim Tjernlund

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=20180904180028.GS26633@bill-the-cat \
    --to=trini@konsulko.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.