ubuntu-drivers-common ftbfs in quantal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-drivers-common (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Quantal |
Fix Released
|
High
|
Martin Pitt |
Bug Description
[re-filing the issue, because of the original issue is a conjoined master with mismatched state]
see bug #1058056
see http://
=======
ERROR: test_hardware_
what-provides HARDWARE_DRIVER
-------
Traceback (most recent call last):
File "/build/
['drivers_
File "/build/
None, lambda p, t, d: True, None)
File "/usr/lib/
return info.invoke(*args, **kwargs)
gi._glib.GError: GDBus.Error:
-------
Ran 36 tests in 541.765s
FAILED (errors=1)
make[1]: *** [override_
make[1]: Leaving directory `/build/
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
pitti:
This is due to the utterly slow and swap-to-death arm builders. Just retry the build, it'll work after a few attempts. I really don't want to disable this test, as it's working fine everywhere else and I want to know whether functionality works on arm platforms as well.
doko:
re-opening. closing as won't fix won't help anything for the release, until the package can be built.
now retried some times, and it always fails in the same place.
Related branches
Changed in ubuntu-drivers-common (Ubuntu Quantal): | |
importance: | Undecided → High |
Changed in ubuntu-drivers-common (Ubuntu Quantal): | |
status: | Confirmed → In Progress |
assignee: | nobody → Martin Pitt (pitti) |
I can reproduce this when adding a "sleep 1" to /usr/bin/aptd's main, to simulate the arm builder slowness.