Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>,
	<auh@yoctoproject.org>, "Trevor Gamblin" <tgamblin@baylibre.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [AUH] python3: upgrading to 3.14.8 SUCCEEDED
Date: Fri, 02 Oct 2026 14:44:42 +0200	[thread overview]
Message-ID: <DLUD1OK99YO3.1QPQV67EMZI06@bootlin.com> (raw)
In-Reply-To: <8d16f142-505a-4806-a419-b237773e5374@est.tech>

On Fri Oct 2, 2026 at 10:22 AM CEST, Jaipaul Cheernam wrote:
>
> On 2026-10-01 19:31, Mathieu Dubois-Briand via lists.openembedded.org wrote:
> I think we need to skip newly added test case in above commit like we 
> did for test_write_read_limited_history in recipe.
>
> # Also fails with editline instead of readline. See:
> # https://github.com/python/cpython/issues/123018
> SKIPPED_TESTS += " \
>      --ignore test_write_read_limited_history \
> "
>

I'm not sure. I tried to compare a build with and without musl, and
history looks broken on musl builds.

So I use the same steps as in the test:

>>> import readline
>>> readline.clear_history()
>>> readline.add_history("first line")
>>> readline.add_history("second line")
>>> readline.write_history_file("/hist")
>>> readline.add_history("third line")
>>> readline.set_history_length(2)
>>> readline.append_history_file(1, "/hist")
>>> readline.clear_history()
>>> readline.read_history_file("/hist")
>>> self.assertEqual(readline.get_history_item(1), "second line")

On the glibc build, I have:
root@qemux86-64:~# cat /hist 
_HiStOrY_V2_
second\040line
third\040line

While on the musl build, I have:
root@qemux86-64:~# cat /hist
_HiStOrY_V2_
_HiStOrY_V2_
third\040line

Now it's funny, as both build are using editline, but the behaviour is
different. It might be that the issue is not just in python.

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



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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01  6:31 [AUH] python3: upgrading to 3.14.8 SUCCEEDED auh
2026-10-01 17:31 ` [OE-core] " Mathieu Dubois-Briand
2026-10-02  8:22   ` Jaipaul Cheernam
2026-10-02 12:44     ` Mathieu Dubois-Briand [this message]

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=DLUD1OK99YO3.1QPQV67EMZI06@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=auh@yoctoproject.org \
    --cc=jaipaul.cheernam@est.tech \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tgamblin@baylibre.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