Poky Project Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: sstate status
Date: Wed, 08 Dec 2010 08:31:49 -0700	[thread overview]
Message-ID: <4CFFA4E5.1000803@mlbassoc.com> (raw)
In-Reply-To: <4CFF9907.3090901@mlbassoc.com>

On 12/08/2010 07:41 AM, Gary Thomas wrote:
> On 12/08/2010 07:06 AM, Paul Eggleton wrote:
>> On Wednesday 08 December 2010 14:02:15 Paul Eggleton wrote:
>>> I have to admit I didn't look closely enough to be sure - I was mainly
>>> testing between two different build machines which don't share the same
>>> native arch, so the native packages were rebuilt anyway. I'm starting a
>>> fresh build now with my new branch to see if I can reproduce your results.
>>
>> FYI my build just finished and it's definitely rebuilding a whole bunch of packages (and not just native ones). More concerningly it seems to have rebuilt git-native and the hash
>> has actually changed, although bitbake-diffsigs doesn't seem to be able to tell me what is different other than the hash itself.
>
> I'm running my own experiments on this branch. It seems that
> something more fundamental is broken. I first ran
> % bitbake poky-image-minimal
> which seemed to go OK although the resulting image.tar.bz2 looks
> surprisingly empty. I've not investigated this fully.
>
> Then in the same tree, nothing else touched, I ran
> % bitbake poky-image-sato
> which generated a ton of messages like these:
> NOTE: package task-base-1.0-r69: task do_populate_sysroot_setscene: Started
> NOTE: Staging package /tmp/sstate_testing/sstate-cache/sstate-task-base-qemuarm-poky-linux-gnueabi-1.0-r69-armv5te-1-f2de7ef77366ff6028dbbf54a0206318_populate-sysroot.tgz does not
> exist
> NOTE: package task-base-1.0-r69: task do_package_setscene: Started
> NOTE: Staging package /tmp/sstate_testing/sstate-cache/sstate-task-base-qemuarm-poky-linux-gnueabi-1.0-r69-armv5te-1-82eff67eab7faa49e63393c34ce384dd_package.tgz does not exist
> etc. I also have seen that if I abort this build, there are
> literally hundreds of setscene tasks pending...
>
> I've put the logs at
> http://www.mlbassoc.com/poky/poky-image-minimal-from-paule-branch
> http://www.mlbassoc.com/poky/poky-image-sato-from-paule-branch

BTW you'll notice that the second build failed (it wasn't done when
I posted this originally):

NOTE: package portmap-6.0-r7: task do_install: Started
ERROR: Task failed: ('function do_install failed', '/tmp/sstate_testing/tmp/work/armv5te-poky-linux-gnueabi/portmap-6.0-r7/temp/log.do_install.26036')
ERROR: Logfile of failure stored in: /tmp/sstate_testing/tmp/work/armv5te-poky-linux-gnueabi/portmap-6.0-r7/temp/log.do_install.26036
Log data follows:
| NOTE: make -e MAKEFLAGS= install DESTDIR=/tmp/sstate_testing/tmp/work/armv5te-poky-linux-gnueabi/portmap-6.0-r7/image
| install -o root -g root -m 0755 portmap /tmp/sstate_testing/tmp/work/armv5te-poky-linux-gnueabi/portmap-6.0-r7/image/sbin
| install: cannot change ownership of `/tmp/sstate_testing/tmp/work/armv5te-poky-linux-gnueabi/portmap-6.0-r7/image/sbin/portmap': Operation not permitted
| make: *** [install] Error 1
| FATAL: oe_runmake failed
| ERROR: Task failed: ('function do_install failed', '/tmp/sstate_testing/tmp/work/armv5te-poky-linux-gnueabi/portmap-6.0-r7/temp/log.do_install.26036')
NOTE: package portmap-6.0-r7: task do_install: Failed

My build host is Fedora 13 with SELinux disabled.

> Query: what sort of machine do you use for this testing? I have a
> Core-2 quad @2.4GHz with 3GB of RAM and it takes me around 5 hours
> to make a full test.
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2010-12-08 15:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 14:02 sstate status Paul Eggleton
2010-12-08 14:06 ` Paul Eggleton
2010-12-08 14:15   ` Tian, Kevin
2010-12-08 14:50     ` Paul Eggleton
2010-12-08 14:52       ` Tian, Kevin
2010-12-08 14:41   ` Gary Thomas
2010-12-08 15:31     ` Gary Thomas [this message]
2010-12-08 15:55     ` Paul Eggleton
2010-12-08 17:14       ` Paul Eggleton
  -- strict thread matches above, loose matches on Subject: below --
2010-12-03 16:34 Paul Eggleton
2010-12-03 22:11 ` Richard Purdie
2010-12-05 11:10   ` Tian, Kevin
2010-12-06  1:29     ` Richard Purdie
2010-12-07  7:46       ` Tian, Kevin
2010-12-07 15:02         ` Richard Purdie
2010-12-08  0:40           ` Tian, Kevin
2010-12-06 16:06   ` Paul Eggleton
2010-12-07 12:46     ` Richard Purdie
2010-12-07 16:36       ` Paul Eggleton
2010-12-08 11:22         ` Tian, Kevin
2010-12-08 11:31           ` Paul Eggleton
2010-12-08 11:41             ` Tian, Kevin
2010-12-03 23:31 ` Gary Thomas
2010-12-04 12:47   ` Gary Thomas
2010-12-05 11:19     ` Tian, Kevin
2010-12-05 12:02       ` Gary Thomas
2010-12-06 11:19         ` Gary Thomas
     [not found]         ` <4CFCC607.9040803@mlbassoc.com>
2010-12-07  7:17           ` Tian, Kevin
2010-12-05 11:07 ` Tian, Kevin

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=4CFFA4E5.1000803@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@yoctoproject.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