Hi,
Le 02/08/2022 à 18:00, Edward Betts a écrit :
[…]
I wonder if it would be possible to routinely run the autopkgtests on s390x,
or another big-endian architecture, for 'Architecture: all' packages and make
the results available.
AFAICT, they already are. E.g. <https://ci.debian.net/packages/p/phpunit/>.
I recently packaged a Python module called sqlite-fts4 written by Simon Willison. The package is pure Python, so is 'Architecture: all', but it
fails on big-endian architectures. The test suite catches this failure.
The bug was spotted by OpenSUSE because they tried to run the test suite on s390x. They filed a bug which upstream has fixed.
https://github.com/simonw/sqlite-fts4/issues/6
Simon has written some posts about this problem.
https://til.simonwillison.net/python/struct-endianness https://til.simonwillison.net/docker/emulate-s390x-with-qemu
It would be nice if the Debian infrastructure could catch this class of bug.
Building the sqlite-fts4 Debian package runs the test suite, and I've configured it to run the tests via autopkgtest.
If these tests are run at build-time, errors halt the build and that provides
Didier 'OdyX' Raboud dixit:
If these tests are run at build-time, errors halt the build and that provides
That may not be enough, though; there are cases where the build
architecture determines artefact endianness (e.g. with PCF bitmap
fonts), and that may even be enough (X servers can load PCFs from reverse-endian builds), but it may be a bug. So you’d ideally use
both.
On Sun, Aug 28, 2022 at 04:56:26PM +0000, Thorsten Glaser wrote:
Didier 'OdyX' Raboud dixit:provides
If these tests are run at build-time, errors halt the build and that
That may not be enough, though; there are cases where the build architecture determines artefact endianness (e.g. with PCF bitmap
fonts), and that may even be enough (X servers can load PCFs from reverse-endian builds), but it may be a bug. So you’d ideally use
both.
Funny thing: there's not a single release architecture that's both
bad-endian and supports X (they do build X related packages because the dependency graph is quite dense, but there are no users). So this
particular problem has solved itself :)
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ You're alive. But that's just a phase. ⠈⠳⣄⠀⠀⠀⠀
Funny thing: there's not a single release architecture that's both
bad-endian and supports X (they do build X related packages because the >dependency graph is quite dense, but there are no users). So this
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 28:25:22 |
Calls: | 6,707 |
Calls today: | 1 |
Files: | 12,239 |
Messages: | 5,352,806 |