resource expression "device.category == 'CARDREADER'" evaluates to false
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Fix Released
|
High
|
Taihsiang Ho | ||
HEXR |
Fix Released
|
High
|
Unassigned |
Bug Description
A SRU automation test skipped this device and showed
job cannot be started: resource expression "device.category == 'CARDREADER'" evaluates to false
(from this URL: https:/
However the machine does has this device and manual test of the device shows it is working.
Steps to reproduce this bug:
1. launch_testrun 12.04.1 desktop -p --plainbox --ppa=stable 201009-6503
2. wait for the automatic installation and testing
3. check the result of the URL above.
Expected result:
SD test is automatically tested.
Actual result:
SD test is skipped.
-- more information --
$ uname -a
Linux 201009-6503 3.2.0-65-generic #98-Ubuntu SMP Wed Jun 11 20:27:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg -l | grep -E 'checkbox|
ii canonical-
ii checkbox 0.17.9.
ii checkbox-
ii checkbox-gui 0.18~ppa~
ii checkbox-ng 0.4~ppa~
ii checkbox-ng-service 0.4~ppa~
ii checkbox-qt 0.17.9.
ii plainbox-
ii plainbox-
ii plainbox-
ii plainbox-
ii python3-checkbox 0.17.9.
ii python3-checkbox-ng 0.4~ppa~
ii python3-
ii python3-plainbox 0.6~ppa~
Related branches
- Zygmunt Krynicki (community): Needs Fixing
- Daniel Manrique: Pending requested
-
Diff: 52 lines (+22/-12)1 file modifiedcheckbox-support/checkbox_support/parsers/udevadm.py (+22/-12)
- Daniel Manrique (community): Needs Fixing
-
Diff: 74 lines (+34/-15)1 file modifiedcheckbox-support/checkbox_support/parsers/udevadm.py (+34/-15)
Changed in plainbox-provider-checkbox: | |
assignee: | nobody → Taihsiang Ho (taihsiangho) |
status: | Confirmed → In Progress |
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Fix Committed |
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Fix Released |
Changed in hexr: | |
status: | Fix Committed → Fix Released |
Hi, can you please run this command?
udevadm info --export-db > udev-1334224.txt
then attach udev-1334224.txt to this bug. I'll run it through the parser and see which devices it's recognizing.
It may be identifying the card reader as a disk device of some sort.