amd64-only test running on i386
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-pyeclib (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
six (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Some tests in d/t/control are not meant to be run on non-amd64 architectures. The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[
print("Skipping {} test for {} architecture"
else:
...
In eoan, at some point during the development cycle, the VM running i386 tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-
...
Get:5 http://
Get:6 http://
Get:7 http://
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/
autopkgtest [09:22:26]: test command7: [------
Traceback (most recent call last):
File "debian/
ec = ECDriver(k=3, m=3, hd=3, ec_type=
File "/usr/lib/
validate=
File "/usr/lib/
instance = object_class(*args, **kwargs)
File "/usr/lib/
validate)
pyeclib.
init: autopkgtest [09:22:26]: test command7: -------
It's probably best to use "dpkg --architecture" for this check.
Changed in six (Ubuntu): | |
status: | New → Invalid |
Added six to the list of affected packages so that this bug will show up in the excuses report as to why six isn't migrating.