Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@ge.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: release 2010-12: tar error
Date: Tue, 21 Dec 2010 11:50:09 +0000	[thread overview]
Message-ID: <4D109471.6010202@ge.com> (raw)
In-Reply-To: <20101206204753.GC29253@denix.org>

On 06/12/10 20:47, Denys Dmytriyenko wrote:
> On Fri, Dec 03, 2010 at 11:44:14AM -0800, Khem Raj wrote:
>> On Fri, Dec 3, 2010 at 7:36 AM, Frans Meulenbroeks
>> <fransmeulenbroeks@gmail.com> wrote:
>>> Not sure if this is reproducible or a race but when building console-image
>>> for minimal for calamari I got:
>>>
>>> ERROR: Function staging_packager failed
>>> NOTE: Task failed: ('function staging_packager failed',
>>> '/home/hudson/jobs/FM_TEST/workspace/tmp/work/calamari-oe-linux-gnuspe/linux-2.6.30-r6/temp/log.staging_packager.27026')
>>> ERROR: Task 601
>>> (/home/hudson/jobs/FM_TEST/workspace/openembedded/recipes/linux/linux_2.6.30.bb,
>>> do_package_stage) failed with 256
>>> NOTE: oestats: task failed, see
>>> http://tinderbox.openembedded.net/packages/1176040/
>>> ERROR: Logfile of failure stored in:
>>> /home/hudson/jobs/FM_TEST/workspace/tmp/work/calamari-oe-linux-gnuspe/linux-2.6.30-r6/temp/log.staging_packager.27026
>>> Log data follows:
>>> | tar: .: file changed as we read it
>>>
>>> NOTE: package linux-2.6.30-r6: task do_package_stage: Failed
>>>
>>> Didn't have time to dig into this. Sry.
>>
>> yes this happens time to time. Its some sort of race condition. I get
>> it sometimes in different packages but never went in deep to fix it.
> 
> I can confirm that this is a long standing race condition, presumably in 
> packaged staging - there were several attempts at fixing it w/o much success.
> 

I recently repeatedly hit this. I'm in the process of setting up some
automated testing which made this particularly annoying. I had
BB_NUMBER_THREADS and PARALLEL_MAKE setup in my local.conf. I think this is
arises when BB_NUMBER_THREADS is set. I've removed it and taken the hit in
build time instead (preferable in my situation). This seems to have stop it
being an issue, but I need to do quite a few more runs to make sure.

Martyn


-- 
Martyn Welch (Principal Software Engineer) | Registered in England and
GE Intelligent Platforms                   | Wales (3828642) at 100
T +44(0)127322748                          | Barbirolli Square, Manchester,
E martyn.welch@ge.com                      | M2 3AB  VAT:GB 927559189



  reply	other threads:[~2010-12-21 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 15:36 release 2010-12: tar error Frans Meulenbroeks
2010-12-03 19:44 ` Khem Raj
2010-12-06 20:47   ` Denys Dmytriyenko
2010-12-21 11:50     ` Martyn Welch [this message]
2010-12-21 22:58       ` Graham Gower
2010-12-22 13:26         ` Martyn Welch

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=4D109471.6010202@ge.com \
    --to=martyn.welch@ge.com \
    --cc=openembedded-devel@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