From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2021-03-03
Date: Fri, 5 Mar 2021 16:14:42 +0100 [thread overview]
Message-ID: <20210305161442.066cc2de@windsurf.home> (raw)
In-Reply-To: <CAEyMn7YFHLJ=SBaB8N4NGaKN=tO_UYAO13-D2-JUnyoLQpoWAA@mail.gmail.com>
On Fri, 5 Mar 2021 16:10:27 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> Indeed. The netopeer package is a bit annoying to install. But I hope
> Jan Kundrat will make his offer come true [1] and provide a better
> solution.
>
> Since the problem currently only occurs on one autobuild host, I would
> leave it alone until then. Is that ok for you? Or should I try to
> patch the problem?
We try when possible to fix or work around the issues, as having noise
in the autobuilders is always a bit annoying. I haven't looked in
details into the problem, so I don't have a particular suggestion to
make, though.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-03-05 15:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 8:15 [Buildroot] [autobuild.buildroot.net] Daily results for 2021-03-03 Thomas Petazzoni
2021-03-04 21:49 ` [Buildroot] Analysis of build " Thomas Petazzoni
2021-03-04 22:26 ` Yann E. MORIN
2021-03-05 8:01 ` Giulio Benetti
2021-03-05 8:36 ` Peter Korsgaard
2021-03-05 7:56 ` Giulio Benetti
2021-03-05 8:55 ` Giulio Benetti
2021-03-05 9:13 ` Giulio Benetti
2021-03-05 9:22 ` Thomas Petazzoni
2021-03-05 16:01 ` Giulio Benetti
2021-03-05 16:13 ` Giulio Benetti
2021-03-05 16:52 ` Giulio Benetti
2021-03-05 9:48 ` Thomas De Schampheleire
2021-03-05 15:10 ` Heiko Thiery
2021-03-05 15:14 ` Thomas Petazzoni [this message]
2021-03-05 15:38 ` Heiko Thiery
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=20210305161442.066cc2de@windsurf.home \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox