From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Olaf Mandel <o.mandel@menlosystems.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] toasterui.py: warn if buildstats is missing
Date: Fri, 28 Oct 2016 10:27:58 +0100 [thread overview]
Message-ID: <1477646878.3717.83.camel@linux.intel.com> (raw)
In-Reply-To: <1477586197-29398-1-git-send-email-o.mandel@menlosystems.com>
On Thu, 2016-10-27 at 16:36 +0000, Olaf Mandel wrote:
> Like for buildhistory and INHERIT, warn if buildstats is missing
> from USER_CLASSES.
>
> Signed-off-by: Olaf Mandel <o.mandel@menlosystems.com>
> ---
> lib/bb/ui/toasterui.py | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/lib/bb/ui/toasterui.py b/lib/bb/ui/toasterui.py
> index 9808f6b..2687faf 100644
> --- a/lib/bb/ui/toasterui.py
> +++ b/lib/bb/ui/toasterui.py
> @@ -168,6 +168,11 @@ def main(server, eventHandler, params):
> logger.warning("buildhistory is not enabled. Please enable
> INHERIT += \"buildhistory\" to see image details.")
> build_history_enabled = False
>
> + userclasseslist, _ = server.runCommand(["getVariable",
> "USER_CLASSES"])
> +
> + if not "buildstats" in userclasseslist.split(" "):
> + logger.warning("buildstats is not enabled. Please enable
> USER_CLASSES += \"buildstats\" to generate build statistics.")
As USER_CLASSES is an intermediate variable whose value becomes part of
the INHERIT assignment it'd be better to check whether buildstats is in
INHERIT, rather than USER_CLASSES.
This should better handle configurations which include buildstats in a
different manner.
> +
> if not params.observe_only:
> params.updateFromServer(server)
> params.updateToServer(server, os.environ.copy())
> --
> 2.1.4
>
next prev parent reply other threads:[~2016-10-28 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 16:36 [PATCH] toasterui.py: warn if buildstats is missing Olaf Mandel
2016-10-28 9:27 ` Joshua Lock [this message]
2016-10-28 14:04 ` [PATCH v2] " Olaf Mandel
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=1477646878.3717.83.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=o.mandel@menlosystems.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 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.