All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Daily results for 2020-09-10
Date: Fri, 11 Sep 2020 10:15:47 +0200	[thread overview]
Message-ID: <20200911101547.77832bc9@windsurf.hq.k.grp> (raw)
In-Reply-To: <38c1b78d-82f6-2d50-a60f-eb6a161d22f8@heine.tech>

On Fri, 11 Sep 2020 09:29:20 +0200
Michael Nosthoff <buildroot@heine.tech> wrote:

> On 11.09.2020 09:08, Thomas Petazzoni wrote:
> >   aarch64    |        host-grpc-1.31.0        | NOK | http://autobuild.buildroot.net/results/c2078e821e0728fe980be2c849c25d82e791a4c2 |     
> >   mips64el   |        host-grpc-1.31.0        | NOK | http://autobuild.buildroot.net/results/b554f6f2fb66892273f7520ad6e36923557b229e |     
> >    x86_64    |        host-grpc-1.31.0        | NOK | http://autobuild.buildroot.net/results/3ebb2880b9b3fd5154979016391dde897e2c039c |       
> 
> All those cases seem to fail with a GNU 4.8.2 host toolchain. I would
> like to reproduce that. On what OS are those build jobs run? Is this
> maybe a Docker Image which I could use?

Yes, Yann had a Docker image that allows to reproduce the issue.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-09-11  8:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11  7:08 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-09-10 Thomas Petazzoni
2020-09-11  7:29 ` Michael Nosthoff
2020-09-11  8:15   ` Thomas Petazzoni [this message]
2020-09-11 12:27     ` Yann E. MORIN
2020-09-11 13:18       ` Michael Nosthoff
2020-09-11 14:21         ` Yann E. MORIN
2020-09-11 21:12           ` Michael Nosthoff
2020-09-11 21:23             ` Yann E. MORIN
2020-09-15 14:15               ` Michael Nosthoff

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=20200911101547.77832bc9@windsurf.hq.k.grp \
    --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.