Hello
I'm trying to understand what's happening to fpdf2:
https://tracker.debian.org/fpdf2
Before the upload I've built it with ``gbp buildpackage --git-pbuilder``
and a freshly updated sid image, and the build was successful, but then
I get
https://buildd.debian.org/status/package.php?p=fpdf2
with the error:
===== 1289 passed, 52 skipped, 3 xfailed, 13 warnings in 187.91s (0:03:07) =====
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.13 3.12" returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_test] Error 25
for comparison, in the pbuilder log there is:
===== 1289 passed, 52 skipped, 3 xfailed, 13 warnings in 171.69s (0:02:51) =====
and the tests are considered successful, and the build continues.
Hello
I'm trying to understand what's happening to fpdf2:
https://tracker.debian.org/fpdf2
Before the upload I've built it with ``gbp buildpackage --git-pbuilder``
and a freshly updated sid image, and the build was successful, but then
I get
https://buildd.debian.org/status/package.php?p=fpdf2
with the error:
===== 1289 passed, 52 skipped, 3 xfailed, 13 warnings in 187.91s (0:03:07) =====
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.13 3.12" returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_test] Error 25
for comparison, in the pbuilder log there is:
===== 1289 passed, 52 skipped, 3 xfailed, 13 warnings in 171.69s (0:02:51) =====
and the tests are considered successful, and the build continues.
(I've also tried a local run of ``autopkgtest ./ -- qemu ../../autopkgtest-unstable.img``, again with a freshly updated image,
and that also considers the tests to be passing, with the same results)
What am I doing wrong?
The "1289 passed, 52 skipped, etc" line is the output of pytest run
with Python 3.12. Before that, pybuild ran pytest with Python 3.13,
and one of the tests failed there; look for 'frozen posixpath'
(without the quotes) in the build log.
Unfortunately, the failure message from pytest is surprisingly unhelpful;
I would have expected it to display the posixpath object as a string,
so one can figure out what the "filename" was instead of the current
Python source file.
I may try reproducing this locally, but I will not be able to do that
until tomorrow at least.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 483 |
Nodes: | 16 (1 / 15) |
Uptime: | 81:02:34 |
Calls: | 9,576 |
Calls today: | 7 |
Files: | 13,666 |
Messages: | 6,142,985 |
Posted today: | 2 |