public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Trevor Gamblin <tgamblin@baylibre.com>
To: yoann.congal@smile.fr, "Marko, Peter" <Peter.Marko@siemens.com>
Cc: "patchtest@automation.yoctoproject.org"
	<patchtest@automation.yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Patchtest results for [OE-core][scarthgap 11/22] cups: allow unknown directives in conf files
Date: Tue, 20 Jan 2026 12:52:45 -0500	[thread overview]
Message-ID: <7b0978c4-3e1c-4147-ad60-da683182ac17@baylibre.com> (raw)
In-Reply-To: <CAMSfU+6qqthiP2bD0VSu4XVJKOutwLHy=O+sByC5LXqJN2X2yg@mail.gmail.com>


On 2026-01-20 07:59, Yoann Congal via lists.openembedded.org wrote:
>
>
> Le mar. 20 janv. 2026 à 13:21, Marko, Peter <Peter.Marko@siemens.com> 
> a écrit :
>
>     False positive as this does not fix CVE, only mentions CVE in
>     commit message.
>
>
> Thanks for the analysis :)
>
>     I'm wondering why this was sent now and not when I submitted the
>     patch.
>     In recent months there is almost 0 emails from patchtest.
>     I guess it's broken and revives only from time to time?
>
>
> Yup, that's it. It was down for a few weeks but looks better now.
Yes, it went down for a bit but is back up. I think it may have missed 
some patch IDs in its tracker, hence why this was sent now.
>
>     Peter
>
>     > -----Original Message-----
>     > From: openembedded-core@lists.openembedded.org <openembedded-
>     > core@lists.openembedded.org> On Behalf Of Patchtest via
>     > lists.openembedded.org <http://lists.openembedded.org>
>     > Sent: Tuesday, January 20, 2026 13:17
>     > To: Yoann Congal <yoann.congal@smile.fr>
>     > Cc: openembedded-core@lists.openembedded.org
>     > Subject: Patchtest results for [OE-core][scarthgap 11/22] cups:
>     allow unknown
>     > directives in conf files
>     >
>     > Thank you for your submission. Patchtest identified one
>     > or more issues with the patch. Please see the log below for
>     > more information:
>     >
>     > ---
>     > Testing patch
>     /home/patchtest/share/mboxes/scarthgap-11-22-cups-allow-
>     > unknown-directives-in-conf-files.patch
>     >
>     > FAIL: test CVE tag format: Missing or incorrectly formatted CVE
>     tag in patch file.
>     > Correct or include the CVE tag in the patch with format: "CVE:
>     CVE-YYYY-XXXX"
>     > (test_patch.TestPatch.test_cve_tag_format)
>     >
>     > PASS: test Signed-off-by presence
>     > (test_mbox.TestMbox.test_signed_off_by_presence)
>     > PASS: test Signed-off-by presence
>     > (test_patch.TestPatch.test_signed_off_by_presence)
>     > PASS: test Upstream-Status presence
>     > (test_patch.TestPatch.test_upstream_status_presence_format)
>     > PASS: test author valid (test_mbox.TestMbox.test_author_valid)
>     > PASS: test commit message presence
>     > (test_mbox.TestMbox.test_commit_message_presence)
>     > 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 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
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#229703): https://lists.openembedded.org/g/openembedded-core/message/229703
> Mute This Topic: https://lists.openembedded.org/mt/117361790/7611679
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [tgamblin@baylibre.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


  reply	other threads:[~2026-01-20 17:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 12:08 [OE-core][scarthgap 00/22] Patch review Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 01/22] python3: patch CVE-2025-12084 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 02/22] python3: patch CVE-2025-13836 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 03/22] util-linux: patch CVE-2025-14104 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 04/22] qemu: ignore CVE-2025-54566 and CVE-2025-54567 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 05/22] glib-2.0: patch CVE-2025-13601 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 06/22] glib-2.0: patch CVE-2025-14087 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 07/22] glib-2.0: patch CVE-2025-14512 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 08/22] dropbear: patch CVE-2019-6111 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 09/22] libpcap: patch CVE-2025-11961 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 10/22] libpcap: patch CVE-2025-11964 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 11/22] cups: allow unknown directives in conf files Yoann Congal
2026-01-20 12:16   ` Patchtest results for " patchtest
2026-01-20 12:21     ` Marko, Peter
2026-01-20 12:59       ` Yoann Congal
2026-01-20 17:52         ` Trevor Gamblin [this message]
2026-01-20 12:08 ` [OE-core][scarthgap 12/22] libarchive: fix CVE-2025-60753 regression Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 13/22] curl: patch CVE-2025-14017 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 14/22] curl: patch CVE-2025-14819 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 15/22] curl: patch CVE-2025-15079 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 16/22] curl: patch CVE-2025-15224 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 17/22] pseudo: Upgrade to version 1.9.1 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 18/22] pseudo: 1.9.0 -> 1.9.2 Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 19/22] pseudo: Update to pull in memleak fix Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 20/22] pseudo: Add hard sstate dependencies for pseudo-native Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 21/22] pseudo: Update to pull in openat2 and efault return code changes Yoann Congal
2026-01-20 12:08 ` [OE-core][scarthgap 22/22] pseudo: Update to pull in 'makewrappers: Fix EFAULT implementation' Yoann Congal

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=7b0978c4-3e1c-4147-ad60-da683182ac17@baylibre.com \
    --to=tgamblin@baylibre.com \
    --cc=Peter.Marko@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patchtest@automation.yoctoproject.org \
    --cc=yoann.congal@smile.fr \
    /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