Re: SetScene tasks hang forever?

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Wed, 2012-05-09 at 10:51 -0700, Rich Pixley wrote:
> On 5/8/12 05:34 , Richard Purdie wrote:
> > On Sun, 2012-05-06 at 10:36 -0700, Rich Pixley wrote:
> >> Any other ideas?
> > Well, this clearly doesn't happen with master or in any combination of
> > the layers most users are using. The logical conclusion would be that
> > there is something in your layer that is somehow triggering this.
> No private layer involved.
> 
> I do have a makefile which encapsulates the environment stuff, but 
> that's it.
> > Of course since that layer is secret and you can't show us it, we have a
> > bit of a problem. Can you reproduce the bug against public code?
> Done.  (Our layer is becoming open, we're committed to it, but it's a 
> long process internally).
> > Are you by any chance setting BB_STAMP_POLICY somewhere?
> Yes.  BB_STAMP_POLICY = "full".
> 
> I'll attach a copy of my local.conf and bblayers.conf.

I'm 95% sure its BB_STAMP_POLICY = "full" causing the problems. The idea
is really that sstate and other recent developments obsolete the "full"
stamp code. I'm not sure it actually gets on with the setscene stamps
the sstate code generates, as I suspect you're discovering.

We could try and fix the "full" policy, or we could just remove it.
Looking at the code for the function that deals with this in
runqueue.py, I can see where problems could occur.

So I guess I'm asking if we should fix that or can we remove it?

Cheers,

Richard