From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: antonin.godard@bootlin.com, openembedded-core@lists.openembedded.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [OE-core] [PATCH] python3: skip flaky test_default_timeout test
Date: Mon, 19 Jan 2026 14:39:35 +0000 [thread overview]
Message-ID: <2e9127c0edb3ddf367f31776094ca23042687212.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260119-skip-python3-test-default-timeout-v1-1-e15fce4cb867@bootlin.com>
On Mon, 2026-01-19 at 15:21 +0100, Antonin Godard via lists.openembedded.org wrote:
> We have been observing intermittent issues with this test on the Autobuilder:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=15885
>
> This is probably due to the Autobuilder being heavily loaded at the time
> of the test.
>
> The logs on the ticket above do not allow us to know which of the two
> "test_default_timeout" tests is failing, so disable both with
> self.skipTest().
>
> Excerpt from `ptest-runner python3`:
>
> test_default_timeout (test.test_multiprocessing_fork.test_manager.WithManagerTestBarrier.test_default_timeout)
> SKIP: Test the barrier's default timeout 'skip flaky timeout test'
>
> [YOCTO #15885]
>
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
> ...001-Skip-flaky-test_default_timeout-tests.patch | 49 ++++++++++++++++++++++
> meta/recipes-devtools/python/python3_3.13.11.bb | 1 +
> 2 files changed, 50 insertions(+)
>
> diff --git a/meta/recipes-devtools/python/python3/0001-Skip-flaky-test_default_timeout-tests.patch b/meta/recipes-devtools/python/python3/0001-Skip-flaky-test_default_timeout-tests.patch
> new file mode 100644
> index 0000000000..4e1bd833b4
> --- /dev/null
> +++ b/meta/recipes-devtools/python/python3/0001-Skip-flaky-test_default_timeout-tests.patch
> @@ -0,0 +1,49 @@
> +From baf2dda48e51fcb17a716e52cc5c4e162a6bb7d3 Mon Sep 17 00:00:00 2001
> +From: Antonin Godard <antonin.godard@bootlin.com>
> +Date: Mon, 19 Jan 2026 11:38:36 +0100
> +Subject: [PATCH] Skip flaky test_default_timeout tests
> +
> +We have been observing issues with this test on the Autobuilder:
> +https://bugzilla.yoctoproject.org/show_bug.cgi?id=15885
> +
> +The logs on the ticket above do not allow us to know which of the two
> +"test_default_timeout" tests is failing, so disable both with
> +self.skipTest().
> +
> +Excerpt from `ptest-runner python3`:
> +
> + test_default_timeout (test.test_multiprocessing_fork.test_manager.WithManagerTestBarrier.test_default_timeout)
> + SKIP: Test the barrier's default timeout 'skip flaky timeout test'
> +
> +Upstream-Status: Inappropriate [OE specific, but might be related to https://github.com/python/cpython/issues/129266#issuecomment-2613058866]
> +
> +Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> +---
> + Lib/test/_test_multiprocessing.py | 1 +
> + Lib/test/lock_tests.py | 1 +
> + 2 files changed, 2 insertions(+)
> +
> +diff --git a/Lib/test/_test_multiprocessing.py b/Lib/test/_test_multiprocessing.py
> +index e8064e7..9ab1f9e 100644
> +--- a/Lib/test/_test_multiprocessing.py
> ++++ b/Lib/test/_test_multiprocessing.py
> +@@ -2259,6 +2259,7 @@ class _TestBarrier(BaseTestCase):
> + """
> + Test the barrier's default timeout
> + """
> ++ self.skipTest('skip flaky timeout test')
> + barrier = self.Barrier(self.N, timeout=0.5)
> + results = self.DummyList()
> + self.run_threads(self._test_default_timeout_f, (barrier, results))
> +diff --git a/Lib/test/lock_tests.py b/Lib/test/lock_tests.py
> +index 8c8f890..43e9b90 100644
> +--- a/Lib/test/lock_tests.py
> ++++ b/Lib/test/lock_tests.py
> +@@ -1165,6 +1165,7 @@ class BarrierTests(BaseTestCase):
> + """
> + Test the barrier's default timeout
> + """
> ++ self.skipTest('skip flaky timeout test')
> + timeout = 0.100
> + barrier = self.barriertype(2, timeout=timeout)
> + def f():
> diff --git a/meta/recipes-devtools/python/python3_3.13.11.bb b/meta/recipes-devtools/python/python3_3.13.11.bb
> index 2fcfd4aba1..2bc2389b7e 100644
> --- a/meta/recipes-devtools/python/python3_3.13.11.bb
> +++ b/meta/recipes-devtools/python/python3_3.13.11.bb
> @@ -30,6 +30,7 @@ SRC_URI = "http://www.python.org/ftp/python/${PV}/Python-${PV}.tar.xz \
> file://0001-test_active_children-skip-problematic-test.patch \
> file://0001-test_readline-skip-limited-history-test.patch \
> file://0001-Generate-data-for-OpenSSL-3.4-and-add-it-to-multissl.patch \
> + file://0001-Skip-flaky-test_default_timeout-tests.patch \
> "
> SRC_URI:append:class-native = " \
> file://0001-Lib-sysconfig.py-use-prefix-value-from-build-configu.patch \
I have the python3.14 upgrade queued in master-next for review so we
may need to test this with the new python version?
Cheers,
Richard
next prev parent reply other threads:[~2026-01-19 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 14:21 [PATCH] python3: skip flaky test_default_timeout test Antonin Godard
2026-01-19 14:39 ` Richard Purdie [this message]
2026-01-19 14:42 ` [OE-core] " Antonin Godard
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=2e9127c0edb3ddf367f31776094ca23042687212.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=antonin.godard@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thomas.petazzoni@bootlin.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