All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Paul Barker" <paul@pbarker.dev>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][wrynose 18/21] python3: use SKIPPED_TESTS instead of test skip patches
Date: Thu, 11 Jun 2026 12:39:40 +0200	[thread overview]
Message-ID: <DJ65ME2CV03O.291OM3MDV8SQL@smile.fr> (raw)
In-Reply-To: <ccf309b775b890e94e6cc0d5e8c13ffc4d4218ce.camel@pbarker.dev>

On Thu Jun 11, 2026 at 10:58 AM CEST, Paul Barker wrote:
> On Thu, 2026-06-11 at 00:55 +0200, Yoann Congal via
> lists.openembedded.org wrote:
>> From: Trevor Gamblin <tgamblin@baylibre.com>
>> 
>> Drop all 13 patches carried for skipping various known ptest failures
>> and replace them with usage of the SKIPPED_TESTS variable, which we have
>> started doing in recent commits (e.g. 40b0815dc9). Most but not all of
>> the test skips are due to load variability, distinguish between them by
>> using multiple SKIPPED_TESTS:append blocks with comments taken from the
>> patch files indicating their purpose. This adds 62 lines to the Python 3
>> recipe, but it also means that we no longer have to maintain the patch
>> files across version upgrades, where they often break due to changes in
>> the test modules upstream.
>
> Hi Yoann,
>
> What's the reason for backporting this (and the following patch) to the
> stable branch?

Hello,

Mainly, it was to make future backports easier to hopefully fix the
AB-INTs we have on python (as it would align wrynose & master for the
python recipe). But I admit this is a weak argument. I don't mind
dropping those now and revisit when we have an actual fix to backport.

>
> Best regards,


-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-06-11 10:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 22:54 [OE-core][wrynose 00/21] Patch review Yoann Congal
2026-06-10 22:54 ` [OE-core][wrynose 01/21] libpcap: fix error message on 32-bit integer overflow Yoann Congal
2026-06-10 22:54 ` [OE-core][wrynose 02/21] lttng-modules: Fix trace_hrtimer_start build failure Yoann Congal
2026-06-10 22:54 ` [OE-core][wrynose 03/21] perf: make libraries for install_headers configurable Yoann Congal
2026-06-10 22:54 ` [OE-core][wrynose 04/21] cups: fix CVE-2026-34978 Yoann Congal
2026-06-10 22:54 ` [OE-core][wrynose 05/21] cups: fix CVE-2026-34979 Yoann Congal
2026-06-10 22:54 ` [OE-core][wrynose 06/21] cups: fix CVE-2026-34980 Yoann Congal
2026-06-10 22:54 ` [OE-core][wrynose 07/21] cups: fix CVE-2026-34990 Yoann Congal
2026-06-10 22:54 ` [OE-core][wrynose 08/21] cups: fix CVE-2026-39314 Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 09/21] cups: fix CVE-2026-39316 Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 10/21] xserver-xorg: upgrade 21.1.21 -> 21.1.22 Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 11/21] bind: upgrade 9.20.22 -> 9.20.23 Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 12/21] libsdl2: Fix compilation error with DirectFB Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 13/21] libsolv: fix CVE-2026-9150 Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 14/21] go: upgrade 1.26.2 -> 1.26.3 Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 15/21] go: upgrade 1.26.3 -> 1.26.4 Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 16/21] python3: upgrade 3.14.4 -> 3.14.5 Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 17/21] python3: Fix ThreadingMock call_count race condition Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 18/21] python3: use SKIPPED_TESTS instead of test skip patches Yoann Congal
2026-06-11  8:58   ` Paul Barker
2026-06-11 10:39     ` Yoann Congal [this message]
2026-06-10 22:55 ` [OE-core][wrynose 19/21] python3: use += instead of :append in SKIPPED_TESTS Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 20/21] python3: sanitize userbase in _sysconfig_vars JSON to avoid host path leak Yoann Congal
2026-06-10 22:55 ` [OE-core][wrynose 21/21] python3: reference upstream ticket in a test skip 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=DJ65ME2CV03O.291OM3MDV8SQL@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    /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.