From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12
Date: Tue, 14 May 2019 17:43:05 +0200 [thread overview]
Message-ID: <20190514174305.4ee8da2b@windsurf> (raw)
In-Reply-To: <CANQCQpZFOf=0zsDVqim7R9MopGDuN6bvPOC1PNV_DO=cPXhm=Q@mail.gmail.com>
Hello,
On Tue, 14 May 2019 09:57:00 -0500
Matthew Weber <matthew.weber@collins.com> wrote:
> > > microblazeel | glibmm | TIM | http://autobuild.buildroot.net/results/e196d77626b877dc3454d21febe20a04877c02a9 |
> >
> > Another weird timeout, this time on Matt's autobuilder. Matt, could you
> > have a look ?
> >
> > But this seems to happen quite regularly, even on other autobuilder
> > machines:
> >
> > http://autobuild.buildroot.net/?reason=glibmm
> >
> > Always on microblazeel, like the timeout on "atop" discussed above. I
> > guess that probably points at a compiler issue, which means it should
> > be reproducible.
> >
>
> Build definitely hung (didn't even need to be on that build machine).
> I'll hopefully get some time to take a deeper look later.
I'd say most likely it's the same Microblaze issue than on atop, which
Giulio has been looking into, and which is in fact related to
BR2_TOOLCHAIN_HAS_GCC_BUG_85180.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-14 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12 Thomas Petazzoni
2019-05-13 11:55 ` Thomas Petazzoni
2019-05-13 12:08 ` Baruch Siach
2019-05-13 12:38 ` Giulio Benetti
2019-05-14 8:45 ` Peter Korsgaard
2019-05-14 14:57 ` Matthew Weber
2019-05-14 15:43 ` Thomas Petazzoni [this message]
2019-05-14 17:12 ` Giulio Benetti
2019-05-14 17:43 ` Giulio Benetti
2019-05-14 21:13 ` Adrian Perez de Castro
2019-05-16 9:41 ` 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=20190514174305.4ee8da2b@windsurf \
--to=thomas.petazzoni@bootlin.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 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.