From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Daily results for 2020-09-10
Date: Fri, 11 Sep 2020 16:21:31 +0200 [thread overview]
Message-ID: <20200911142131.GA10548@scaer> (raw)
In-Reply-To: <1f704b79-d506-698e-38c3-8d4ee1146802@heine.tech>
Michael, All,
On 2020-09-11 15:18 +0200, Michael Nosthoff spake thusly:
> On 11.09.2020 14:27, Yann E. MORIN wrote:
> > Michael, All,
> >
> > On 2020-09-11 10:15 +0200, Thomas Petazzoni spake thusly:
> >> On Fri, 11 Sep 2020 09:29:20 +0200
> >> Michael Nosthoff <buildroot@heine.tech> wrote:
> >>> On 11.09.2020 09:08, Thomas Petazzoni wrote:
> >>>> mips64el | host-grpc-1.31.0 | NOK | http://autobuild.buildroot.net/results/b554f6f2fb66892273f7520ad6e36923557b229e |
> > Thanks for looking into this. Here's a simple way to reproduce:
> > $ curl https://pastebin.com/raw/JMe512Pt >foo/Dockerfile
> Thanks for the Dockerfile.
> Wouldn't it make sense to include the used Dockerfile with the autobuild
> results?
Because the autobuilders do not (all) run in docker.
For example, my autobuilder (on which the host-grpc build issue happens)
is not running in docker, so there is no Dockerfile that created it. It
was manually created in November 2015 with debbootstrap.
The Dockerfile I provided was made after the fact, a few months ago,
last May.
> Concerning the host-grpc issue:
>
> With the Dockerfile I was able to reproduce the issue.
> In comparison on a debian jessie with gcc 4.8.5 this problem does not occur.
>
> From what I found on the protobuf issue tracker this seems to be an
> issue which hits people pretty randomly even with newer (mostly clang)
> compilers:
>
> https://github.com/protocolbuffers/protobuf/issues/6074
Yeah, I had already found those issues bacj when I was investigating:
https://github.com/protocolbuffers/protobuf/issues/5353
https://github.com/protocolbuffers/protobuf/issues/5923
And also:
https://github.com/grpc/grpc/issues/22781
> So currently I have no real idea how to fix this...
I also already spent quite some time investigating this issue, and I
have no clue...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-09-11 14:21 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
2020-09-11 12:27 ` Yann E. MORIN
2020-09-11 13:18 ` Michael Nosthoff
2020-09-11 14:21 ` Yann E. MORIN [this message]
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=20200911142131.GA10548@scaer \
--to=yann.morin.1998@free.fr \
--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.