Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
	"Jan-Simon Möller" <jsmoeller@linuxfoundation.org>,
	"Anuj Mittal" <anuj.mittal@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/3] insane: Improve patch warning/error handling
Date: Thu, 19 Jan 2023 10:24:23 +0100	[thread overview]
Message-ID: <20230119102423.3493565d@booty> (raw)
In-Reply-To: <20230118142221.1926666-1-richard.purdie@linuxfoundation.org>

Hello Richard,

On Wed, 18 Jan 2023 14:22:19 +0000
"Richard Purdie" <richard.purdie@linuxfoundation.org> wrote:

> Currently, whilst patch errors or warnings are shown, the errors don't stop builds.
> The configuration isn't very configurable from WARN_QA and ERROR_QA either.
> 
> This patch:
>  * Uses the standard mechanisms to handle the patch fuzz warnings/errors
>  * Makes Upstream-Status checking configurable from WARN/ERROR_QA
>  * Allows that checking to be used with non-core layers
>  * Makes patch-fuzz an error by default
>  * Enables warnings for missing Upstream-Status in non-core layer patches by default
> 
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
>  meta/classes-global/insane.bbclass | 27 ++++++++++++++++++---------
>  1 file changed, 18 insertions(+), 9 deletions(-)
> 
> diff --git a/meta/classes-global/insane.bbclass b/meta/classes-global/insane.bbclass
> index ada8a7ef4e4..e1295f85392 100644
> --- a/meta/classes-global/insane.bbclass
> +++ b/meta/classes-global/insane.bbclass
> @@ -29,11 +29,12 @@
>  WARN_QA ?= " libdir xorg-driver-abi buildpaths \
>              textrel incompatible-license files-invalid \
>              infodir build-deps src-uri-bad symlink-to-sysroot multilib \
> -            invalid-packageconfig host-user-contaminated uppercase-pn patch-fuzz \
> +            invalid-packageconfig host-user-contaminated uppercase-pn \
>              mime mime-xdg unlisted-pkg-lics unhandled-features-check \
>              missing-update-alternatives native-last missing-ptest \
>              license-exists license-no-generic license-syntax license-format \
>              license-incompatible license-file-missing obsolete-license \
> +            patch-status-noncore \

AB testing with this patch applied revealed a few Upstream-Status
warnings:

- 5 in meta-agl-core:
  https://autobuilder.yoctoproject.org/typhoon/#/builders/120/builds/2272/steps/13/logs/stdio

- 3 in meta-intel:
  https://autobuilder.yoctoproject.org/typhoon/#/builders/100/builds/3968/steps/13/logs/stdio

Jan-Simon, Anuj, can you look at those patches and maybe fix the Upstream-Status?

Richard, this patch didn't trigger any problems in my test branch. Now
I'm going to remove it from my testing branch in order to avoid
warnings on issues we already know, unless you prefer me too keep it
and ignore the above mentioned warnings until they are fixed in the
respective layers.

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2023-01-19  9:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 14:22 [PATCH 1/3] insane: Improve patch warning/error handling Richard Purdie
2023-01-18 14:22 ` [PATCH 2/3] pseudo: Update to pull in linux-libc-headers race fix Richard Purdie
2023-01-18 14:22 ` [PATCH 3/3] pseudo: Switch back to the master branch Richard Purdie
2023-01-18 16:46   ` [OE-core] " Luca Ceresoli
2023-01-18 17:04     ` Richard Purdie
2023-01-19  9:24 ` Luca Ceresoli [this message]
2023-01-19  9:57   ` [OE-core] [PATCH 1/3] insane: Improve patch warning/error handling Richard Purdie
2023-01-19 13:55     ` Bruce Ashfield
2023-01-19 14:40       ` Richard Purdie
2023-01-19 14:52         ` Bruce Ashfield
2023-01-19 14:55           ` Richard Purdie
2023-01-19 14:56       ` Ross Burton
2023-01-20 14:26         ` Bruce Ashfield
2023-01-20 19:10           ` Alexander Kanavin
2023-01-20 19:29             ` Bruce Ashfield
2023-01-20 19:38               ` Alexander Kanavin
2023-01-20 23:00                 ` Richard Purdie
2023-01-22 12:46                   ` Peter Kjellerstedt
2023-01-22 22:19                     ` Richard Purdie
2023-01-23  8:08                       ` Mikko Rapeli
2023-01-23  9:18                         ` Alexander Kanavin
     [not found] ` <173BAB83B1A056B8.24231@lists.openembedded.org>
2023-01-19  9:52   ` Luca Ceresoli

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=20230119102423.3493565d@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=anuj.mittal@intel.com \
    --cc=jsmoeller@linuxfoundation.org \
    --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