All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <roosesweb@gmail.com>, <openembedded-core@lists.openembedded.org>
Cc: "Ross Burton" <ross.burton@arm.com>, "Thomas Roos" <thomas@roosesweb.de>
Subject: Re: [OE-core] [PATCH v2] python3-cython: upgrade 3.2.9 -> 3.3.1
Date: Thu, 12 Nov 2026 10:16:59 +0100	[thread overview]
Message-ID: <DMT4AZG7HHGE.3SZFW7TTHZV29@bootlin.com> (raw)
In-Reply-To: <20261108214236.1294076-1-thomas@roosesweb.de>

On Sun Nov 8, 2026 at 10:42 PM CET, Thomas Roos via openembedded-core wrote:
> PyAV 19.0.0, which Home Assistant 2026.11 pins for its stream and
> generic camera integrations, requires Cython 3.3: its generated code
> uses __Pyx_BEGIN_CRITICAL_SECTION, which Cython 3.2 does not provide.
>
> 3.3.1 contains the upstream fixes for the non-deterministic generated
> code that held back the 3.3.0 upgrade (cython#8045, #7982, #8025).
>
> Cython 3.3 still fails intermittently when it builds itself in
> parallel (cython#7997; #8008 and #8013 are not merged). Clean builds
> of python3-cython-native with PARALLEL_MAKE = "-j 32" failed 6 out of
> 20 times with 3.3.1 (and 8 out of 20 with 3.3.0), with the refnanny
> error seen on the autobuilder. With PARALLEL_MAKE = "" all 20 builds
> passed, so build serially for now.
>
> Refresh the line numbers of the build path patch for 3.3.1.
>
> License-Update: none, LICENSE.txt is unchanged.
> AI-Generated: Claude Code, Claude Opus 5.5
> Signed-off-by: Thomas Roos <thomas@roosesweb.de>
> ---

Hi Thomas,

Thanks for the new version.

It does look better, but it looks like we still see some intermittent
reproducibility issues. I had it on my branch for a few days, and
suddenly we had a failed test:

AssertionError: The following deb packages are different and not in exclusion list:
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/python3-cython-dbg_3.3.1-r0_amd64.deb
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/python3-cython-src_3.3.1-r0_amd64.deb
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/python3-cython_3.3.1-r0_amd64.deb
The following ipk packages are different and not in exclusion list:
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/ipk/./x86-64-v3/python3-cython-dbg_3.3.1-r0_x86-64-v3.ipk
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/ipk/./x86-64-v3/python3-cython-src_3.3.1-r0_x86-64-v3.ipk
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/ipk/./x86-64-v3/python3-cython_3.3.1-r0_x86-64-v3.ipk
The following rpm packages are different and not in exclusion list:
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/rpm/./x86_64_v3/python3-cython-3.3.1-r0.x86_64_v3.rpm
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/rpm/./x86_64_v3/python3-cython-dbg-3.3.1-r0.x86_64_v3.rpm
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/rpm/./x86_64_v3/python3-cython-src-3.3.1-r0.x86_64_v3.rpm

https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/5342
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20261111-opb4ps2w/packages/diff-html/

Can you have a look at the issue?

Thanks,
Mathieu


-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2026-11-12  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08 19:25 [PATCH] python3-cython: upgrade 3.2.9 -> 3.3.1 Thomas Roos
2026-11-08 21:42 ` [PATCH v2] " Thomas Roos
2026-11-12  9:16   ` Mathieu Dubois-Briand [this message]
2026-11-12 15:26     ` [OE-core] " Ross Burton

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=DMT4AZG7HHGE.3SZFW7TTHZV29@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=roosesweb@gmail.com \
    --cc=ross.burton@arm.com \
    --cc=thomas@roosesweb.de \
    /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.