public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <peter.marko@siemens.com>,
	"patchtest@automation.yoctoproject.org"
	<patchtest@automation.yoctoproject.org>,
	"Hongxu Jia" <hongxu.jia@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Patchtest results for [PATCH 3/3] gnupg: 2.5.14 -> 2.5.17
Date: Tue, 10 Feb 2026 11:40:26 +0100	[thread overview]
Message-ID: <DGB7V2ANTTCH.34VU08DOUAPYS@smile.fr> (raw)
In-Reply-To: <AS1PR10MB5697AD37C0ECCBC9E8B71456FD62A@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>

On Tue Feb 10, 2026 at 11:36 AM CET, Peter Marko via lists.openembedded.org wrote:
>
>
>> -----Original Message-----
>> From: openembedded-core@lists.openembedded.org <openembedded-
>> core@lists.openembedded.org> On Behalf Of Patchtest via
>> lists.openembedded.org
>> Sent: Tuesday, February 10, 2026 11:01
>> To: Hongxu Jia <hongxu.jia@windriver.com>
>> Cc: openembedded-core@lists.openembedded.org
>> Subject: [OE-core] Patchtest results for [PATCH 3/3] gnupg: 2.5.14 -> 2.5.17
>> 
>> Thank you for your submission. Patchtest identified one
>> or more issues with the patch. Please see the log below for
>> more information:
>
> Ideally mention security fixes: CVE-2026-24882 and CVE-2026-24883.

Yes! Please do that.

That helps me a lot to find upstream commits when reviewing patchs for
stable branches.

Thanks!

>
> Peter
>
>> 
>> ---
>> Testing patch /home/patchtest/share/mboxes/3-3-gnupg-2.5.14---2.5.17.patch
>> 
>> FAIL: test commit message presence: Please include a commit message on your
>> patch explaining the change
>> (test_mbox.TestMbox.test_commit_message_presence)
>> 
>> PASS: test Signed-off-by presence
>> (test_mbox.TestMbox.test_signed_off_by_presence)
>> PASS: test author valid (test_mbox.TestMbox.test_author_valid)
>> PASS: test commit message user tags
>> (test_mbox.TestMbox.test_commit_message_user_tags)
>> PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
>> PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
>> PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
>> PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)
>> PASS: test target mailing list (test_mbox.TestMbox.test_target_mailing_list)
>> 
>> SKIP: pretest pylint: No python related patches, skipping test
>> (test_python_pylint.PyLint.pretest_pylint)
>> SKIP: test CVE tag format: No new CVE patches introduced
>> (test_patch.TestPatch.test_cve_tag_format)
>> SKIP: test Signed-off-by presence: No new CVE patches introduced
>> (test_patch.TestPatch.test_signed_off_by_presence)
>> SKIP: test Upstream-Status presence: No new CVE patches introduced
>> (test_patch.TestPatch.test_upstream_status_presence_format)
>> SKIP: test bugzilla entry format: No bug ID found
>> (test_mbox.TestMbox.test_bugzilla_entry_format)
>> SKIP: test pylint: No python related patches, skipping test
>> (test_python_pylint.PyLint.test_pylint)
>> SKIP: test series merge on head: Merge test is disabled for now
>> (test_mbox.TestMbox.test_series_merge_on_head)
>> 
>> ---
>> 
>> Please address the issues identified and
>> submit a new revision of the patch, or alternatively, reply to this
>> email with an explanation of why the patch should be accepted. If you
>> believe these results are due to an error in patchtest, please submit a
>> bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category
>> under 'Yocto Project Subprojects'). For more information on specific
>> failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank
>> you!


-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-02-10 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10  9:50 [PATCH 1/3] vte: 0.82.2 -> 0.83.90 Hongxu Jia
2026-02-10  9:50 ` [PATCH 2/3] dpkg: 1.22.21 -> 1.23.5 Hongxu Jia
2026-02-10  9:50 ` [PATCH 3/3] gnupg: 2.5.14 -> 2.5.17 Hongxu Jia
2026-02-10 10:00   ` Patchtest results for " patchtest
2026-02-10 10:36     ` [OE-core] " Marko, Peter
2026-02-10 10:40       ` Yoann Congal [this message]
2026-02-11  2:43         ` [PATCH v2] " Hongxu Jia
2026-02-11  2:35       ` [OE-core] Patchtest results for [PATCH 3/3] " Hongxu Jia
2026-02-10  9:54 ` [OE-core] [PATCH 1/3] vte: 0.82.2 -> 0.83.90 Alexander Kanavin
2026-02-11  2:23   ` Hongxu Jia

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=DGB7V2ANTTCH.34VU08DOUAPYS@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patchtest@automation.yoctoproject.org \
    --cc=peter.marko@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox