All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>,
	Edgar Bonet <bonet@grenoble.cnrs.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Daily results for 2021-09-17
Date: Sat, 18 Sep 2021 22:25:22 +0200	[thread overview]
Message-ID: <243665c1-0af1-12df-aa4f-4e6c509d13ca@gmail.com> (raw)
In-Reply-To: <20210918102819.GJ1053080@scaer>

Hello Edgar, Yann, All,

Le 18/09/2021 à 12:28, Yann E. MORIN a écrit :
> Edgar, All,
> 
> +Romain
> 
> On 2021-09-18 10:19 +0200, Edgar Bonet spake thusly:
>> The autobuilder wrote:
>>> Detail of defconfig failures for master
>>> ---------------------------------------
>>>
>>>                         defconfig |                        link to the job                        | orph?
>>> ----------------------------------+---------------------------------------------------------------+------
>>>                       aarch64_efi | https://gitlab.com/buildroot.org/buildroot/-/jobs/1597248798  |      
>>>        acmesystems_acqua_a5_512mb | https://gitlab.com/buildroot.org/buildroot/-/jobs/1597248800  |      
>>> [...]
>>
>> There may be a problem on the autobuilder. Most of those links point to
>> build logs that are truncated, and do not show any error message.
>>
>> I just tried one of the failed defconfigs (acmesystems_acqua_a5_512mb)
>> using the exact same Buildroot commit as the autobuilder did
>> (c483318d09). It all went out smoothly.
> 
> 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.

I believe we can use gitlab shared runner for jobs that can be finished in less
than 3h and use our gitlab runner for longer jobs.
Currently it take more than 24h to complete all defconfigs jobs...

Best regards,
Romain

> 
> Regards,
> Yann E. MORIN.
> 

_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-09-18 20:25 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 [this message]
2021-09-18 20:51       ` Yann E. MORIN
2021-09-18 21:10         ` Yann E. MORIN
2021-09-18 21:18         ` Peter Korsgaard

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=243665c1-0af1-12df-aa4f-4e6c509d13ca@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=bonet@grenoble.cnrs.fr \
    --cc=buildroot@buildroot.org \
    --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.