From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: bitbake-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [bitbake-devel] ValueError: insecure string pickle with latest bitbake
Date: Sun, 23 Feb 2014 09:25:33 +0000 [thread overview]
Message-ID: <1393147533.5181.10.camel@ted> (raw)
In-Reply-To: <20140223090640.GR3854@jama>
On Sun, 2014-02-23 at 10:06 +0100, Martin Jansa wrote:
> On Sat, Feb 22, 2014 at 01:07:36PM +0100, Martin Jansa wrote:
> > Hi,
> >
> > last couple of days many of my jenkins builds failed with exception like
> > this:
> >
> > ERROR: An uncaught exception occured in runqueue, please see the failure below:
> > ERROR: Running idle function
> > Traceback (most recent call last):
> > File "/home/jenkins/oe/shr-core-branches/shr-core/bitbake/lib/bb/cooker.py", line 1182, in buildTargetsIdle(server=<ProcessServer(ProcessServer-2, started)>, rq=<bb.runqueue.RunQueue instance at 0x16a95d40>, abort=False):
> > try:
> > > retval = rq.execute_runqueue()
> > except runqueue.TaskFailure as exc:
> > File "/home/jenkins/oe/shr-core-branches/shr-core/bitbake/lib/bb/runqueue.py", line 1093, in RunQueue.execute_runqueue():
> > try:
> > > self.teardown_workers()
> > except:
> > File "/home/jenkins/oe/shr-core-branches/shr-core/bitbake/lib/bb/runqueue.py", line 925, in RunQueue.teardown_workers():
> > self.workerpipe = None
> > > self._teardown_worker(self.fakeworker, self.fakeworkerpipe)
> > self.fakeworker = None
> > File "/home/jenkins/oe/shr-core-branches/shr-core/bitbake/lib/bb/runqueue.py", line 906, in RunQueue._teardown_worker(worker=<subprocess.Popen object at 0xcb4e690>, workerpipe=<bb.runqueue.runQueuePipe instance at 0x11c17710>):
> > while worker.returncode is None:
> > > workerpipe.read()
> > worker.poll()
> > File "/home/jenkins/oe/shr-core-branches/shr-core/bitbake/lib/bb/runqueue.py", line 2095, in runQueuePipe.read():
> > while index != -1 and self.queue.startswith("<event>"):
> > > event = pickle.loads(self.queue[7:index])
> > bb.event.fire_from_worker(event, self.d)
> > ValueError: insecure string pickle
> >
> > and it repeats the same exception very quickly (generated 3GB log in ~ hour)
> >
> > It doesn't happen always, it seems to be triggered in different places in build.
> >
> > Anyone else seeing this as well?
> >
> > I'll add some debug output around it and wait for it to happen again.
>
> I got one example now (not sure if this is the only one):
>
> Because it shows runrpmdeps and I'm the only one so far seeing this, I guess it's caused by:
> http://lists.openembedded.org/pipermail/openembedded-core/2014-February/089632.html
> I'll try to revert that one from my builds
Ah, it that function is called as:
processed = list(pool.imap(oe.package.filedeprunner, pkglist))
i.e. we have multiple processes each running this function. If we print
output, the output stream has no synchronisation and can hence be
corrupted which would explain the value error. You can see an <event>
appear half way through your output...
Cheers,
Richard
prev parent reply other threads:[~2014-02-23 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 12:07 ValueError: insecure string pickle with latest bitbake Martin Jansa
2014-02-23 9:06 ` Martin Jansa
2014-02-23 9:25 ` Richard Purdie [this message]
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=1393147533.5181.10.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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