[Bug 2024207] [NEW] s390x autopkgtest regression of libflame vs glibc in Jammy
Simon Chopin
2024207 at bugs.launchpad.net
Fri Jun 16 14:57:42 UTC 2023
Public bug reported:
The libflame autopgktests on Jammy are now failing on s390x against
glibc 2.35-0ubuntu3.2.
It's triggering a timeout in the numpy-with-libflame test suite. To
reproduce, you need python3-numpy, libflame1 and libflame-dev install.
The issue seems to be in
numpy/f2py/tests/test_compile_function.py::test_f2py_init_compile. To be
able to investigate this, I had to change /usr/lib/python3/dist-
packages/numpy/_pytesttester.py, line 183:
- pytest_args += ["-m", label]
+ pytest_args += ["-k", label]
and then I used the following Python script to reproduce:
#!/usr/bin/python3
import numpy as np
np.test("full", verbose=3, extra_argv=['numpy/f2py/tests/test_compile_function.py::test_f2py_init_compile'])
I haven't managed to go further yet, except that I know that the bug
doesn't seem to trigger if running under strace.
** Affects: glibc (Ubuntu)
Importance: Undecided
Assignee: Simon Chopin (schopin)
Status: Fix Released
** Affects: glibc (Ubuntu Jammy)
Importance: Critical
Status: Triaged
** Tags: foundations-todo regression-proposed update-excuse
** Also affects: glibc (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu Jammy)
Importance: Undecided => Critical
** Changed in: glibc (Ubuntu)
Importance: Critical => Undecided
** Changed in: glibc (Ubuntu Jammy)
Status: New => Triaged
** Changed in: glibc (Ubuntu)
Status: Triaged => Fix Released
** Tags added: regression-proposed update-excuse
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/2024207
Title:
s390x autopkgtest regression of libflame vs glibc in Jammy
Status in glibc package in Ubuntu:
Fix Released
Status in glibc source package in Jammy:
Triaged
Bug description:
The libflame autopgktests on Jammy are now failing on s390x against
glibc 2.35-0ubuntu3.2.
It's triggering a timeout in the numpy-with-libflame test suite. To
reproduce, you need python3-numpy, libflame1 and libflame-dev install.
The issue seems to be in
numpy/f2py/tests/test_compile_function.py::test_f2py_init_compile. To
be able to investigate this, I had to change /usr/lib/python3/dist-
packages/numpy/_pytesttester.py, line 183:
- pytest_args += ["-m", label]
+ pytest_args += ["-k", label]
and then I used the following Python script to reproduce:
#!/usr/bin/python3
import numpy as np
np.test("full", verbose=3, extra_argv=['numpy/f2py/tests/test_compile_function.py::test_f2py_init_compile'])
I haven't managed to go further yet, except that I know that the bug
doesn't seem to trigger if running under strace.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2024207/+subscriptions
More information about the foundations-bugs
mailing list