ubuntu-drivers-common FTBFS randomly, racy test-suite?

Bug #1071997 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-drivers-common (Ubuntu)
Fix Released
High
Martin Pitt
Raring
Fix Released
High
Martin Pitt

Bug Description

https://launchpad.net/ubuntu/raring/+source/ubuntu-drivers-common/1:0.2.71ubuntu1

afaics this is not just with python3.3, but with python3.2 as well.

Tags: ftbfs
summary: - ubuntu-drivers-common FTBFS in raring on 32bit archs
+ ubuntu-drivers-common FTBFS randomly, racy test-suite?
Changed in ubuntu-drivers-common (Ubuntu Raring):
assignee: nobody → Martin Pitt (pitti)
Revision history for this message
Martin Pitt (pitti) wrote :

Actually they fail on a completely different reason:

make[2]: Leaving directory `/build/buildd/ubuntu-drivers-common-0.2.71build1/share/hybrid'
running clean
/bin/sh: 1: python3.2: not found
make[1]: *** [override_dh_auto_clean] Error 127

https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.2.71build1

It's weird that this only happens on i386 and armhf, but not the other architectures. It does build-depen on python3-all, so something seems to be wrong with that metapackage?

Revision history for this message
Martin Pitt (pitti) wrote :

Sorry, that was the wrong version, python3-all build dep was added in :0.2.71ubuntu1. That built fine.

Revision history for this message
Martin Pitt (pitti) wrote :

I don't have a failure log, and it wasn't copied here, so we need to wait until a build actually fails again.

Changed in ubuntu-drivers-common (Ubuntu Raring):
status: Confirmed → Incomplete
Revision history for this message
Martin Pitt (pitti) wrote :

The previous upload from Dmitry also built fine. However, I just found a race condition locally:

======================================================================
FAIL: test_devices_detect_plugins (ubuntu_drivers.ToolTest)
ubuntu-drivers devices includes custom detection plugins
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/martin/ubuntu/build-area/ubuntu-drivers-common-0.2.72/tests/ubuntu_drivers.py", line 773, in test_devices_detect_plugins
    self.assertGreater(special_off, 0, out)
AssertionError: 0 not greater than 0 : == special.py ==
driver : picky - third-party free
driver : special - third-party free

== /tmp/tmpxkjt12/devices/white ==
modalias : pci:v00001234d00sv00000001sd00bc00sc00i00
driver : vanilla - third-party free

== /tmp/tmpxkjt12/devices/graphics ==
vendor : NVIDIA Corporation
model : GT218 [GeForce 8400 GS]
modalias : pci:nvidia
driver : nvidia-current - third-party free recommended
driver : xserver-xorg-video-nouveau - distro free builtin

== /tmp/tmpxkjt12/devices/black ==
modalias : usb:v9876dABCDsv01sd02bc00sc01i05
driver : bcmwl-kernel-source - third-party free
driver : chocolate - third-party free

As there is no other information available, I consider this bug to apply to this race condition.

Changed in ubuntu-drivers-common (Ubuntu Raring):
status: Incomplete → In Progress
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-drivers-common - 1:0.2.72

---------------
ubuntu-drivers-common (1:0.2.72) raring; urgency=low

  [ Matthias Klose ]
  * Build-depend on python3-all.

  [ Dmitrijs Ledkovs ]
  * Use /usr/bin/python3 shebang.

  [ Martin Pitt ]
  * debian/tests/system: Fix duplicate output of error message for test
    failures.
  * tests/ubuntu_drivers.py, test_devices_detect_plugins(): Fix failure if
    special.py occurs first in the output. This bug was triggered by Python
    3.3's new hash randomization behaviour. (LP: #1071997)
  * UbuntuDrivers/detect.py: Fix UnicodeDecodeError crash when encountering a
    package with invalid UTF-8 encoding. Just skip those packages instead. Add
    test to tests/ubuntu_drivers.py.
 -- Martin Pitt <email address hidden> Wed, 07 Nov 2012 15:47:19 +0100

Changed in ubuntu-drivers-common (Ubuntu Raring):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.