From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-12-23
Date: Mon, 25 Dec 2017 13:16:47 +0100 [thread overview]
Message-ID: <460285ee-009d-0e5a-3c16-95fb5dee7579@gmail.com> (raw)
In-Reply-To: <CANQCQpYAVCagCrqYUyuzRaMTFXzYxraBC21cjAhRXJtP6N6msA@mail.gmail.com>
Hi Matthew,
Le 25/12/2017 ? 02:46, Matthew Weber a ?crit?:
> Romain,
>
> On Sun, Dec 24, 2017 at 4:36 AM, Romain Naour <romain.naour@gmail.com> wrote:
>> Hi All,
>>
>> Le 24/12/2017 ? 08:00, Thomas Petazzoni a ?crit :
>>> Hello,
>>>
>>> Build statistics for 2017-12-23
>>> ===============================
> [snip]
>>> powerpc | liburiparser-0.8.1 | TIM | http://autobuild.buildroot.net/results/e7816d6a15d2a96ca9a401e95955c75d54e7d6da |
>>> x86_64 | make[2]: *** [libtests/buil... | TIM | http://autobuild.buildroot.net/results/fded34f8e5da52737f4c40107e28ad77a223d64b |
>>> x86_64 | make[2]: *** [Makefile:71: ... | TIM | http://autobuild.buildroot.net/results/52f9379d98a1826e1d0faa60ba89a8d5ac09895e |
>> The default timeout value seems too short for my autobuilder.
>
> I've got a autobr patchset I'll send out in the next couple days that
> removes the timeout and makes it based on updates to the
> build-time.log. I think I've got enough test coverage at this point.
> My largo autobuilder has been running for a couple day and handling
> 8+hr builds as well as successful/timeouts.
Great thanks!
For now, I increased the timeout to 12h but it's annoying especially for the
host-ti-cgt-pru issue :-/
Best regards,
Romain
>
> Matt Weber
>
next prev parent reply other threads:[~2017-12-25 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2017-12-23 Thomas Petazzoni
2017-12-24 10:36 ` Romain Naour
2017-12-25 1:46 ` Matthew Weber
2017-12-25 12:16 ` Romain Naour [this message]
2017-12-25 17:44 ` Matthew Weber
2017-12-26 17:24 ` Romain Naour
2017-12-30 3:50 ` Matthew Weber
2018-01-03 12:54 ` Romain Naour
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=460285ee-009d-0e5a-3c16-95fb5dee7579@gmail.com \
--to=romain.naour@gmail.com \
--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.