All of lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-11-15
       [not found] <5dcfa2a9.1c69fb81.7eabb.0dddSMTPIN_ADDED_MISSING@mx.google.com>
@ 2019-11-16 12:14 ` Fabio Estevam
  2019-11-17 14:34   ` Arnout Vandecappelle
  0 siblings, 1 reply; 2+ messages in thread
From: Fabio Estevam @ 2019-11-16 12:14 UTC (permalink / raw)
  To: buildroot

Hi Thomas and Arnout,

On Sat, Nov 16, 2019 at 4:18 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:

> Build failures related to your defconfigs:
>
>                         defconfig |                        link to the job
> ----------------------------------+--------------------------------------------------------------
>                  imx6-sabresd_qt5 |  https://gitlab.com/buildroot.org/buildroot/-/jobs/351579609

Received this report for the second time.

The build is taking more than 6 hours.

Should I ignore it?

Thanks

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-11-15
  2019-11-16 12:14 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-11-15 Fabio Estevam
@ 2019-11-17 14:34   ` Arnout Vandecappelle
  0 siblings, 0 replies; 2+ messages in thread
From: Arnout Vandecappelle @ 2019-11-17 14:34 UTC (permalink / raw)
  To: buildroot



On 16/11/2019 13:14, Fabio Estevam wrote:
> Hi Thomas and Arnout,
> 
> On Sat, Nov 16, 2019 at 4:18 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> 
>> Build failures related to your defconfigs:
>>
>>                         defconfig |                        link to the job
>> ----------------------------------+--------------------------------------------------------------
>>                  imx6-sabresd_qt5 |  https://gitlab.com/buildroot.org/buildroot/-/jobs/351579609
> 
> Received this report for the second time.
> 
> The build is taking more than 6 hours.

 I'm trying to debug it, but there's not much information available after the
fact...

 It could be a real timeout, because there are 4 runners going in parallel on
that machine (which has 32 cores).

 The annoying thing is that artifacts aren't uploaded if the build times out...
And even the log is not complete - because of the output filtering we do, the
output is buffered and the last bit isn't there yet.

 So, indeed, not much we can do except to ignore the failure :-(

 Any ideas to improve the reliability of our tests are very welcome!

 Regards,
 Arnout

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-11-17 14:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <5dcfa2a9.1c69fb81.7eabb.0dddSMTPIN_ADDED_MISSING@mx.google.com>
2019-11-16 12:14 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-11-15 Fabio Estevam
2019-11-17 14:34   ` Arnout Vandecappelle

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.