Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] insane.bbclass: write QA issues to log file only when they are in ERROR_QA or WARN_QA
Date: Mon, 21 Aug 2017 22:07:29 +0100	[thread overview]
Message-ID: <1503349649.32591.71.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170821205624.19892-1-Martin.Jansa@gmail.com>

On Mon, 2017-08-21 at 22:56 +0200, Martin Jansa wrote:
> * QA check which aren't included in WARN_QA and ERROR_QA are shown
>   during the build only as NOTE message (not shown at all with
> default
>   knotty setting), so it might be surprising to see them later in
> qa.log
>   file
> 
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  meta/classes/insane.bbclass | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

I've just been having a look at this and I think its by design, all
messages are put into the log but at differing log levels. I think the
correct thing to do may be to filter it as you proposed in your CI
system.

Any other opinions?

Cheers,

Richard


  reply	other threads:[~2017-08-21 21:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21  6:56 [PATCH] insane.bbclass: write QA issues to log file only when thei are in ERROR_QA or WARN_QA Martin Jansa
2017-08-21  7:01 ` Martin Jansa
2017-08-21 20:56 ` [PATCHv2] insane.bbclass: write QA issues to log file only when they " Martin Jansa
2017-08-21 21:07   ` Richard Purdie [this message]
2017-08-21 21:13     ` Martin Jansa
2017-08-21 21:23       ` Richard Purdie
2017-08-21 21:27         ` 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=1503349649.32591.71.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=martin.jansa@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