From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-06
Date: Sat, 8 Nov 2014 18:47:41 +0100 [thread overview]
Message-ID: <20141108184741.66cf1357@free-electrons.com> (raw)
In-Reply-To: <545C9CAE.3070303@imgtec.com>
Dear Vicente Olivert Riera,
On Fri, 7 Nov 2014 10:19:26 +0000, Vicente Olivert Riera wrote:
> On 11/07/2014 07:30 AM, Thomas Petazzoni wrote:
> > Build statistics for 2014-11-06
>
> > mipsel | ola-0.8.33 | TIM | http://autobuild.buildroot.net/results/edb374fba996973c21b7b4ed13d5d07c457793a0/
>
> ^[[3m>>> ola 0.8.33 Autoreconfiguring^[[23m
> make: ***
> [/home/tmp/buildroot-test/instance-0/output/build/ola-0.8.33/.stamp_configured]
> Terminated
>
> No error message. It looks like the autobuilder stopped suddenly.
See the result status: it's "TIM" and not "NOK". This means that the
build too longer than 4 hours, so it was interrupted by the
autobuild-run logic. You should simply ignore such results.
>
> > mipsel | rt-tests-0.83 | NOK | http://autobuild.buildroot.net/results/445bbbb0e6370cc2d1caf4ca66f59b8441f9dcda/
> > mipsel | rt-tests-0.83 | NOK | http://autobuild.buildroot.net/results/88b67de17d7059b2aeb41c483e4c275e5d2f2ee1/
> > mipsel | rt-tests-0.83 | NOK | http://autobuild.buildroot.net/results/e6cb3215fcefd76805abee98b277b810366e456c/
>
> I keep reporting this every day. The autobuilder which is reporting
> these failures is not updated with the latest version of the
> autobuilder-run script.
>
> I don't know who owns this autobuilder, but please, fix it so we will
> not see the same useless reports gain and again.
The autobuild-run script has now been updated today on all autobuilders,
except on Peter autobuilders (I didn't receive an answer from Peter to
my e-mail sent to the autobuilder "maintainers").
> > mips64el | tstools-1_11 | NOK | http://autobuild.buildroot.net/results/e4ee0ae40ac9d58b3182db52d5a39e6ac3692f60/
>
> "Fatal error: can't create obj/esfilter.o: No such file or directory"
>
> I think this is a race condition problem due to the "obj" directory not
> being created in time. I have reported the issue upstream.
>
> https://code.google.com/p/tstools/issues/detail?id=29
If this is a race condition, we could switch to using $(MAKE1) for this
package until the issue gets resolved upstream.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-08 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-06 Thomas Petazzoni
2014-11-07 10:19 ` Vicente Olivert Riera
2014-11-07 12:15 ` Peter Korsgaard
2014-11-08 17:47 ` Thomas Petazzoni [this message]
2014-11-08 20:59 ` Peter Korsgaard
2014-11-09 9:45 ` Thomas Petazzoni
2014-11-09 10:26 ` Peter Korsgaard
2014-11-09 10:35 ` Thomas Petazzoni
2014-11-09 11:24 ` Peter Korsgaard
2014-11-10 15:50 ` Vicente Olivert Riera
2014-11-10 18:11 ` Thomas Petazzoni
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=20141108184741.66cf1357@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox