From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>
Cc: "sanil.kumar" <sanil.kumar@huawei.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Re-execution of tasks - test report and results
Date: Sat, 31 Mar 2012 16:34:02 +0100 [thread overview]
Message-ID: <1333208042.18082.234.camel@ted> (raw)
In-Reply-To: <CAOSpxdYtrYctG3V=cKTvSPaNdimVDdP-MgCM0HQYdL3szAFVjg@mail.gmail.com>
On Sat, 2012-03-31 at 08:04 -0700, Steve Sakoman wrote:
> On Sat, Mar 31, 2012 at 7:07 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > As some people have noticed, there are some rebuild issues happening due
> > to sstate and the use of hashes in the stamp files. By this I mean the
> > case where due to some checksum change, some task gets rerun and the
> > task was not written to run a second time.
>
> For the set of recipes I typically build with my autobuild script I
> found it necessary to add code to do a -c cleansstate on the following
> recipes:
>
> shadow-native
> boost
> gcc
> git
> man-pages
> net-tools
> sqlite
> wget
>
> There seems to be a good amount of overlap with your list, but there
> are a few that are not on your list.
Hmm, yes. We already have a bug open against git but I'd like to
understand shadow-native and sqlite. If you have the failure logs for
those two, I think it would be worth opening bugs for them.
Cheers,
Richard
next prev parent reply other threads:[~2012-03-31 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 14:07 Re-execution of tasks - test report and results Richard Purdie
2012-03-31 15:04 ` Steve Sakoman
2012-03-31 15:34 ` Richard Purdie [this message]
2012-03-31 15:59 ` Steve Sakoman
2012-03-31 16:55 ` Richard Purdie
2012-04-02 3:45 ` Richard Purdie
2012-04-02 9:02 ` Paul Eggleton
2012-04-02 11:59 ` Richard Purdie
2012-04-06 18:56 ` Otavio Salvador
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=1333208042.18082.234.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sanil.kumar@huawei.com \
--cc=steve@sakoman.com \
/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