All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Romain Naour <romain.naour@gmail.com>,
	Edgar Bonet <bonet@grenoble.cnrs.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Daily results for 2021-09-17
Date: Sat, 18 Sep 2021 23:18:40 +0200	[thread overview]
Message-ID: <87ee9lshu7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210918205146.GZ1053080@scaer> (Yann E. MORIN's message of "Sat, 18 Sep 2021 22:51:46 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,


 >> > If you look at the top of the build log, you'll notice that hose
 >> > failures all occur on the gcc160 runner.
 >> > 
 >> > I'm adding Romain in Cc ; IIRC, he already noticed something fishy going
 >> > on with gcc160. Romain?
 >> 
 >> Indeed but there is nothing I can do. I don't have access to this machine.
 >> gcc160 is not an autobuilder but a gitlab runner.

 > Ah, but Peter and Thomas do have access to that machine, I think (I
 > don't), and I think Peter is running tthe gitlab runner there...

 > Peter?

No, Thomas is. I don't have access to gcc160.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2021-09-18 21:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18  7:02 [Buildroot] [autobuild.buildroot.net] Daily results for 2021-09-17 Thomas Petazzoni
2021-09-18  8:19 ` Edgar Bonet
2021-09-18 10:28   ` Yann E. MORIN
2021-09-18 20:25     ` Romain Naour
2021-09-18 20:51       ` Yann E. MORIN
2021-09-18 21:10         ` Yann E. MORIN
2021-09-18 21:18         ` Peter Korsgaard [this message]

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=87ee9lshu7.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=bonet@grenoble.cnrs.fr \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=yann.morin.1998@free.fr \
    /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.