From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] insane: Improve patch-status layer filtering
Date: Tue, 20 Jun 2023 22:16:04 +0200 [thread overview]
Message-ID: <20230620221604.751c44f4@booty> (raw)
In-Reply-To: <20230619140602.2669368-2-richard.purdie@linuxfoundation.org>
Hi Richard,
On Mon, 19 Jun 2023 15:06:02 +0100
"Richard Purdie" <richard.purdie@linuxfoundation.org> wrote:
> Now that we have layer overrides, we can easily enable patch-status in
> ERROR_QA without the hardcoded code making it easier for other layers
> to opt into the checks.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I love the cleanup this patch introduces, however I'm afraid it seems
to be causing some failures on selftest:
AssertionError: Command 'bitbake dos2unix -c patch' returned non-zero exit status 1:
...
ERROR: dos2unix-7.5.0-r0 do_patch: QA Issue: Missing Upstream-Status in patch
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/5367/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/5402/steps/15/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/5325/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5375/steps/15/logs/stdio
Luca
PS: I noticed you seems to already have a fix under test on
origin/master-next!
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-06-20 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 14:06 [PATCH 1/2] bitbake.conf: Add layer-<layername> override support Richard Purdie
2023-06-19 14:06 ` [PATCH 2/2] insane: Improve patch-status layer filtering Richard Purdie
2023-06-19 16:16 ` [OE-core] " Ross Burton
2023-06-20 20:16 ` Luca Ceresoli [this message]
2023-06-20 22:27 ` Richard Purdie
2023-06-21 8:58 ` Martin Jansa
2023-06-21 9:06 ` Richard Purdie
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=20230620221604.751c44f4@booty \
--to=luca.ceresoli@bootlin.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 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.