storage tests are running against MMC readers still on Oneiric Alpha 3

Bug #822948 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
High
Marc Tardif

Bug Description

Running checkbox on Oneiric alpha 3 and I noticed that the storage tests (storage_device_*, disk_smart_* and benchmark_*) are running against the MMC reader on the Latitude 2120.

I thought we'd fixed this... but it needs to be fixed somehow. Running these tests against non-existant devices wastes testers time, and also provides false feedback when the tester gets a message that storage_device_sdb failed (when sdb doesn't actually exist).

Tags: oneiric

Related branches

Revision history for this message
Jeff Lane  (bladernr) wrote :

Marked High because we need to get this fixed before freeze.

Changed in checkbox:
importance: Undecided → High
Jeff Lane  (bladernr)
tags: added: oneiric
Ara Pulido (ara)
Changed in checkbox:
assignee: nobody → Canonical Hardware Certification (canonical-hw-cert)
milestone: none → 0.12.6
status: New → Triaged
Marc Tardif (cr3)
Changed in checkbox:
assignee: Canonical Hardware Certification (canonical-hw-cert) → Marc Tardif (cr3)
Revision history for this message
Marc Tardif (cr3) wrote :

First, this problem seems to be specific to the 10ec:5208 PCI device which has an explicit udev rule to set the ID_DISK_FLASH environment variable. The problem with detecting this variable is that it is only defined for the block which is a child of the actual physical device. Since the udev parser reads the output of udevadm as a stream, state must somehow be preserved between devices. In other words, somekind of support needs to be added for the attributes of a device to be gathered across multiple parts of the udevadm output.

Marc Tardif (cr3)
Changed in checkbox:
status: Triaged → In Progress
Marc Tardif (cr3)
Changed in checkbox:
status: In Progress → Fix Committed
Marc Tardif (cr3)
Changed in checkbox:
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.