All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-10-28
Date: Mon, 29 Oct 2018 09:40:44 -0700	[thread overview]
Message-ID: <CA+h8R2pcuGTzowu+S4-cerB07PVs0obsZHQKDhB+=R_MrN6=qg@mail.gmail.com> (raw)
In-Reply-To: <20181029070026.A6EF0209B0@mail.bootlin.com>

Hi,

On Mon, Oct 29, 2018 at 12:00 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
>       x86_64 |       docker-containerd-v1.1.3 | http://autobuild.buildroot.net/results/9f8ac26c691b699ac9953c5a6f5ec42f1b50e55e
>       x86_64 |      docker-engine-v17.05.0-ce | http://autobuild.buildroot.net/results/16b07236e62a1f334e3a6a7708faf909e3c7f677
>       x86_64 |      docker-engine-v17.05.0-ce | http://autobuild.buildroot.net/results/816b4162daf30842bfe261e4fa42493fdd3fbb3a
>       x86_64 |      docker-engine-v17.05.0-ce | http://autobuild.buildroot.net/results/5c921fc04bc7bbdfee08451e270cf8a6ddb569d5

These are the same "invalid operation" Go compiler bug that we have
seen before. I will investigate if updating Go fixes the issue, and
spin a patch. for 1.11.1.

In the meantime, has there been any further consideration to this
patch, which affects both of these packages:

 - https://patchwork.ozlabs.org/patch/969253/

Thanks,
Christian

       reply	other threads:[~2018-10-29 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181029070026.A6EF0209B0@mail.bootlin.com>
2018-10-29 16:40 ` Christian Stewart [this message]
2018-10-30 17:05   ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-10-28 Peter Korsgaard
     [not found] <20181029070026.9C8E12099B@mail.bootlin.com>
2018-10-29  9:16 ` Sébastien Szymanski
2018-10-29  9:30   ` Baruch Siach

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='CA+h8R2pcuGTzowu+S4-cerB07PVs0obsZHQKDhB+=R_MrN6=qg@mail.gmail.com' \
    --to=christian@paral.in \
    --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.