From: "Mike Crowe" <yocto@mac.mcrowe.com>
To: Jacob Kroon <jacob.kroon@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] rm_work causes image tasks to re-run
Date: Fri, 22 May 2020 21:12:43 +0100 [thread overview]
Message-ID: <20200522201243.GB21451@mcrowe.com> (raw)
In-Reply-To: <b1fcf4c9-9d0a-742b-fa36-1325b09457a1@gmail.com>
On Friday 22 May 2020 at 19:02:47 +0200, Jacob Kroon wrote:
> Hi Mike,
>
> On 5/22/20 10:13 AM, Mike Crowe via lists.openembedded.org wrote:
> > When we have rm_work enabled all image tasks are built every time. This has
> > been happening since at least warrior and is still happening as of master
> > today (8fc19639f47b959a141dae231395bbababa644e1).
> >
> > Steps to reproduce:
> >
> > bitbake core-image-minimal
> > bitbake core-image-minimal
> > echo 'INHERIT += "rm_work"' >> conf/local.conf
> > bitbake core-image-minimal
> > bitbake core-image-minimal
> >
> > The second invocation of bitbake doesn't build anything at all (as would be
> > expected.)
> >
> > The fourth invocation of bitbake always builds:
> >
> > Sstate summary: Wanted 43 Found 43 Missed 0 Current 436 (100% match, 100% complete)
> > NOTE: Executing Tasks
> > NOTE: Setscene tasks completed
> > NOTE: Running noexec task 1750 of 2000 (/fast2/mac/git/oe-core/meta/recipes-core/images/core-image-minimal.bb:do_rm_work_all)
> > NOTE: Running task 1998 of 2000 (/fast2/mac/git/oe-core/meta/recipes-core/images/core-image-minimal.bb:do_populate_lic_deploy)
> > NOTE: recipe core-image-minimal-1.0-r0: task do_populate_lic_deploy: Started
> > NOTE: recipe core-image-minimal-1.0-r0: task do_populate_lic_deploy: Succeeded
> > NOTE: Running task 1999 of 2000 (/fast2/mac/git/oe-core/meta/recipes-core/images/core-image-minimal.bb:do_rm_work)
> > NOTE: recipe core-image-minimal-1.0-r0: task do_rm_work: Started
> > NOTE: recipe core-image-minimal-1.0-r0: task do_rm_work: Succeeded
> > NOTE: Running noexec task 2000 of 2000 (/fast2/mac/git/oe-core/meta/recipes-core/images/core-image-minimal.bb:do_build)
> > NOTE: Tasks Summary: Attempted 2000 tasks of which 1996 didn't need to be rerun and all succeeded.
> >
> > If I teach rm_work.bbclass to also skip files matching
> > "*do_populate_lic_deploy*" then this problem goes away. However, I have
> > form for breaking things in rm_work so I suspect that this isn't the
> > correct fix. Is there a better one?
> >
> > Thanks.
> >
> > Mike.
> >
>
> Since I'm the last guy touching rm_work.bbclass ...
>
> I don't see the rebuilds in my images. Although I do see
>
> core-image-minimal.bb:do_populate_lic_deploy
>
> being run, there is no regeneration of the rootfs images.
I was originally investigating on warrior where the do_rootfs task does run
unnecessarily. It turns out that if I cherry-pick the three subsequent
rm_work changes from master back to warrior then it behaves the same as
master. I shall do that in our tree.
Is it possible to avoid the do_populate_lic_deploy task running
unnecessarily on master too?
Thanks.
Mike.
prev parent reply other threads:[~2020-05-22 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 8:13 rm_work causes image tasks to re-run Mike Crowe
2020-05-22 17:02 ` [OE-core] " Jacob Kroon
2020-05-22 20:12 ` Mike Crowe [this message]
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=20200522201243.GB21451@mcrowe.com \
--to=yocto@mac.mcrowe.com \
--cc=jacob.kroon@gmail.com \
--cc=openembedded-core@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