[Buildroot] [PATCH 1/1] support/testing: remove arc_summary from ZFS tests

[Buildroot] [PATCH 1/1] support/testing: remove arc_summary from ZFS tests

[José Luis Salvador Rufo]

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",
         ]
         for cmd in cmds:
             self.assertRunOk(cmd, timeout=self.timeout)
-- 
2.51.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] support/testing: remove arc_summary from ZFS tests

[Romain Naour via buildroot]

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?

Best regards,
Romain


>          ]
>          for cmd in cmds:
>              self.assertRunOk(cmd, timeout=self.timeout)

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] support/testing: remove arc_summary from ZFS tests

[Waldemar Brodkorb]

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.

best regards
 Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] support/testing: remove arc_summary from ZFS tests

[Romain Naour via buildroot]

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.

Best regards,
Romain


> 
> best regards
>  Waldemar

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] support/testing: remove arc_summary from ZFS tests

[Waldemar Brodkorb]

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