Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Martin Jansa <Martin.Jansa@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [RFC][PATCH] sstatesig.py: show an error instead of warning when sstate manifest isn't found
Date: Fri, 12 Mar 2021 17:41:50 -0500	[thread overview]
Message-ID: <20210312224150.GB4892@denix.org> (raw)
In-Reply-To: <27cd8d13140defc517650f2a1ef76c1d58d9928a.camel@linuxfoundation.org>

On Fri, Feb 26, 2021 at 03:53:38PM +0000, Richard Purdie wrote:
> On Tue, 2021-02-23 at 14:51 +0100, Martin Jansa wrote:
> > On Tue, Feb 23, 2021 at 02:35:53PM +0100, Martin Jansa via lists.openembedded.org wrote:
> > > * not sure if there are some valid use-cases for missing manifest, but
> > >   recently I'm seeing increasing number of build failures where something
> > >   from native recipe is missing (seen it with pseudo, autoconf, nodejs
> > >   recently) and the only indication that something is wrong (before showing
> > >   sometimes misleading error like:
> > >   recipe-sysroot-native/usr/bin/node: No such file or directory
> > >   is this warning:
> > >   NOTE: Running task 7844 of 12431 (/meta-oe/meta-oe/recipes-devtools/nodejs/nodejs_12.20.2.bb:do_prepare_recipe_sysroot)
> > >   NOTE: recipe nodejs-12.20.2-r0: task do_prepare_recipe_sysroot: Started
> > >   WARNING: nodejs-12.20.2-r0 do_prepare_recipe_sysroot: Manifest /BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-nodejs-native.populate_sysroot not found in x86_64 x86_64_ubuntu-18.04 (variant '')?
> > >   NOTE: Running task 7845 of 12431 (/meta-oe/meta-oe/recipes-devtools/nodejs/nodejs_12.20.2.bb:do_unpack)
> > >   NOTE: recipe nodejs-12.20.2-r0: task do_unpack: Started
> > >   WARNING: nodejs-12.20.2-r0 do_prepare_recipe_sysroot: Manifest /BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-nodejs-native.populate_sysroot not found in x86_64 x86_64_ubuntu-18.04 (variant '')?
> > >   NOTE: recipe nodejs-12.20.2-r0: task do_prepare_recipe_sysroot: Succeeded
> > > 
> > >   if I rebuild that native dependency, then it gets fixed and I don't
> > >   see these failures in clean builds (as without sstate and with empty
> > >   TMPDIR), only in incremental builds
> > > 
> > > * but if there isn't valid reason for missing manifest file, then I think
> > >   it would be better to error early (or even bb.fatal())
> > 
> > Looks like this warning was first introduced in 2014:
> > https://git.openembedded.org/openembedded-core/commit/?id=79ea036de331bde65a88fb777647dc099ef05acf
> > then extended and updated for RSS in:
> > https://git.openembedded.org/openembedded-core/commit/?id=809746f56df4b91af014bf6a3f28997d6698ac78
> > then added for package management in:
> > https://git.openembedded.org/openembedded-core/commit/?id=85e72e129362db896b0d368077033e4a2e373cf9
> > and then unified last 2 to common function in:
> > https://git.openembedded.org/openembedded-core/commit/?id=68150bac7444f089f19c789e9f6602d59f605d7a
> 
> I merged this. There were cases where the warning showed in cases where
> there wasn't a problem but I think we've fixed all those now.

Richard, Martin,

Can you please point me to the right way of fixing this? I've been seeing 
this warning before and since it is now an error and backported to Dunfell, 
it breaks builds one in a while.

-- 
Denys

  reply	other threads:[~2021-03-12 22:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166663E8BC670D0D.6890@lists.openembedded.org>
2021-02-23 13:51 ` [OE-core] [RFC][PATCH] sstatesig.py: show an error instead of warning when sstate manifest isn't found Martin Jansa
2021-02-26 15:53   ` Richard Purdie
2021-03-12 22:41     ` Denys Dmytriyenko [this message]
2021-03-12 23:21       ` Martin Jansa
2021-03-15 12:31 ` Martin Jansa

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=20210312224150.GB4892@denix.org \
    --to=denis@denix.org \
    --cc=Martin.Jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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