From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Is sstate broken
Date: Tue, 08 Mar 2011 17:29:47 -0800 [thread overview]
Message-ID: <1299634187.602.546.camel@rex> (raw)
In-Reply-To: <4D70CE46.7040104@mlbassoc.com>
On Fri, 2011-03-04 at 04:34 -0700, Gary Thomas wrote:
> On 03/03/2011 06:59 PM, Zhai, Edwin wrote:
> > Gary Thomas wrote:
> >> On 02/27/2011 11:07 PM, Zhai, Edwin wrote:
> >> > Thanks for trying this.
> >> > sstate function is a little bit fragile recently. I'll look at it after fixing some other bugs.
> >>
> >> Any progress on this?
> >>
> >> Should I file this as a bug?
> >>
> >
> > We have one http://bugzilla.pokylinux.org/show_bug.cgi?id=788
>
> Yes, that addresses the random errors (which don't seem to have any affect)
>
> However, even without those errors, the sstate information is not being
> used at all. In my experiment, a new tree (with the old sstate pointed
> to by SSTATE_MIRRORS) is executing a full build every time.
>
> Did I miss something?
This should be fixed by the couple of recent changes in master, if you
could check this is working I'd appreciate it as we are getting close to
the release and I'd like this to be working.
Cheers,
Richard
next prev parent reply other threads:[~2011-03-09 1:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 15:14 Is sstate broken Gary Thomas
2011-02-28 6:07 ` Zhai, Edwin
2011-03-03 12:56 ` Gary Thomas
2011-03-04 1:59 ` Zhai, Edwin
2011-03-04 11:34 ` Gary Thomas
2011-03-09 1:29 ` Richard Purdie [this message]
2011-03-09 18:42 ` Gary Thomas
2011-03-09 19:04 ` Richard Purdie
2011-03-09 19:30 ` [poky] " Koen Kooi
2011-03-09 19:30 ` Koen Kooi
2011-03-09 21:51 ` [poky] " Khem Raj
2011-03-09 21:51 ` Khem Raj
2011-03-09 23:04 ` [poky] " Richard Purdie
2011-03-09 23:04 ` Richard Purdie
2011-03-09 20:26 ` Gary Thomas
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=1299634187.602.546.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.