From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [ANNOUNCE] Autobuilder script available, join the autobuilder effort!
Date: Sat, 21 Jun 2014 19:20:52 +0200 [thread overview]
Message-ID: <20140621192052.3bd3a17f@free-electrons.com> (raw)
In-Reply-To: <CANQCQpaOQD73SWyE5QSv1CVb8DG1MggsAxdzkb5yy7J9DhANTQ@mail.gmail.com>
Dear Matthew Weber,
Thanks for your report!
On Fri, 20 Jun 2014 16:03:34 -0500, Matthew Weber wrote:
> I seem to get the following output. It looks like the build is right
> before the spot where it is doing the initial "make
> O=./instance-#/output -C ./buildroot". If I manually go into the
> instance#/output folder and do a "make", things seem to look like
> they're working as expected (building packages/downloading archives,
> etc). So my theory is something in my shell environment or the fact
> I'm using python2.6 with that subprocess..... One thing I noticed
> when I got this error was that the resulting logfile in the output
> folder is empty. I added a test write to this file before line 327
> and I saw what I wrote. So it looks like the subprocess isn't getting
> called successfully. Since I'm going to run the script on a newer
> server that has python2.7, this email is probably just a FYI and I'll
> retest once I'm setup to test on that server.
The builds on the Free Electrons build server are running inside an old
Debian chroot which also uses Python 2.6 (2.6.6 to be exact), and it's
working fine.
> Process Process-1:
> Traceback (most recent call last):
> File "/usr/lib/python2.6/multiprocessing/process.py", line 232, in _bootstrap
> self.run()
> File "/usr/lib/python2.6/multiprocessing/process.py", line 88, in run
> self._target(*self._args, **self._kwargs)
> File "./autobuild-run", line 437, in run_instance
> ret = do_build(instance, instance_log)
> File "./autobuild-run", line 327, in do_build
> stdout=f, stderr=f)
Are you sure you're using the latest version of the script? The code at
lines 327 and 437 do not match what your exception stack is showing.
But I'm a bit surprised, because I don't think I've made any changes to
the script since I made the public announcement on the Buildroot
mailing list.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-21 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 19:23 [Buildroot] [ANNOUNCE] Autobuilder script available, join the autobuilder effort! Thomas Petazzoni
2014-06-17 10:24 ` Thomas De Schampheleire
2014-06-17 11:00 ` Thomas Petazzoni
2014-06-18 7:31 ` Thomas De Schampheleire
2014-06-18 8:25 ` Thomas Petazzoni
2014-06-18 8:47 ` Thomas De Schampheleire
2014-06-18 8:51 ` Thomas Petazzoni
2014-06-18 9:23 ` Thomas De Schampheleire
2014-06-18 11:51 ` Thomas De Schampheleire
2014-06-19 12:40 ` Thomas Petazzoni
2014-06-20 21:03 ` Matthew Weber
2014-06-21 17:20 ` Thomas Petazzoni [this message]
2014-06-22 18:37 ` Matthew Weber
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=20140621192052.3bd3a17f@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