From: Waldemar Brodkorb <wbx@openadk.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: Josss Luis Salvador Rufo <salvador.joseluis@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] support/testing: remove arc_summary from ZFS tests
Date: Fri, 19 Sep 2025 20:22:27 +0200 [thread overview]
Message-ID: <aM2fY2H8TTWOUdKr@waldemar-brodkorb.de> (raw)
In-Reply-To: <bcc3f93b-dfd9-45ea-b668-447b07f3009a@smile.fr>
Hi,
Romain Naour wrote,
> Hello Waldemar, All,
>
> Le 15/09/2025 à 22:54, Waldemar Brodkorb a écrit :
> > Hi,
> > Romain Naour wrote,
> >
> >> Hello José, All,
> >>
> >> Le 14/09/2025 à 06:20, José Luis Salvador Rufo a écrit :
> >>> This patch replace the [1] patch.
> >>>
> >>> The Python 3.13 interpreter itself segfaults at runtime when compiled
> >>> with uClibc on the aarch64 platform.
> >>>
> >>> To keep TestZfsUclibc, the execution of the arc_summary command has
> >>> been removed from the ZFS tests. This command only prints some ARC
> >>> stats anyway.
> >>>
> >>> Fixes:
> >>> https://gitlab.com/buildroot.org/buildroot/-/jobs/11271124859 (TestZfsUclibc)
> >>>
> >>> [1] https://lists.buildroot.org/pipermail/buildroot/2025-September/786396.html
> >>>
> >>> Signed-off-by: José Luis Salvador Rufo <salvador.joseluis@gmail.com>
> >>> ---
> >>> support/testing/tests/package/test_zfs.py | 2 --
> >>> 1 file changed, 2 deletions(-)
> >>>
> >>> diff --git a/support/testing/tests/package/test_zfs.py b/support/testing/tests/package/test_zfs.py
> >>> index 1b907ac4de..9feae49e86 100644
> >>> --- a/support/testing/tests/package/test_zfs.py
> >>> +++ b/support/testing/tests/package/test_zfs.py
> >>> @@ -56,8 +56,6 @@ class TestZfsBase(infra.basetest.BRTest):
> >>> "zpool scrub -w pool",
> >>> "sha256sum -c /tmp/urandom.sha256",
> >>> "zpool status -v",
> >>> - # Check PyZFS
> >>> - "arc_summary",
> >>
> >> Actually the test is not about ARC stats reported by arc_summary script but a
> >> check if PyZFS doesn't trigger some Python exception due to missing python
> >> runtime dependency (if PyZFS is working as expected when python3 is enabled).
> >>
> >> This also remove the PyZFS test for musl and Glibc that are working well.
> >>
> >> If arc_summary is removed from the test, then we should also remove
> >> BR2_PACKAGE_PYTHON3=y from TestZfsBase.
> >>
> >> The TestZfsBase is fine as is, we should not try to remove PyZFS test for the
> >> sake of uClibc-ng.
> >>
> >> Actually, I'm worried about the aarch64 port on uClibc-ng. It's possible that
> >> the issue we discover on python3 package can happen at runtime on other packages.
> >>
> >> If you really want to keep TestZfsUclibc, the PyZFS test should be only executed
> >> by TestZfsGlibc and TestZfsMusl. I'm not sure it worth the effort. Lets remove
> >> TestZfsUclibc for now and hope the issue will be fixed in uClibc-ng in upcoming
> >> releases. Then TestZfsUclibc can be added back.
> >>
> >> Thoughts?
> >
> > I found the bug in uClibc-ng ld.so code for aarch64. I will do a
> > release this weekend when I have finished testing.
>
> Nice, Thanks for the help.
>
> Actually, I'm happy to mark this series as rejected from patchwork. :)
>
> Let us know when your patch is ready.
Patch sent to the BR mailinglist.
best regards
Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-09-19 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 4:20 [Buildroot] [PATCH 1/1] support/testing: remove arc_summary from ZFS tests José Luis Salvador Rufo
2025-09-14 12:23 ` Romain Naour via buildroot
2025-09-15 20:54 ` Waldemar Brodkorb
2025-09-16 11:41 ` Romain Naour via buildroot
2025-09-19 18:22 ` Waldemar Brodkorb [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=aM2fY2H8TTWOUdKr@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
--cc=salvador.joseluis@gmail.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 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.