some device not have vid/pid in it's nature, and that shouldn't be failure
Bug #1908961 reported by
Yuan-Chen Cheng
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Checkbox Provider - Base |
Expired
|
Medium
|
Sylvain Pineau | ||
| OEM Priority Project |
Confirmed
|
Medium
|
Yuan-Chen Cheng | ||
Bug Description
per test case com.canonical.
if VID/PID is missing, it will be treated as a failure.
Some devices will provide virtual UART and connect the device there.
For such a device, this test case will always fail, which is wrong.
Ex:
path: /devices/
bus: bluetooth
category: BLUETOOTH
and they won't have vid/pid by it's nature.
| tags: | added: oem-priority originate-from-1908385 somerville |
Revision history for this message
| Sylvain Pineau (sylvain-pineau) wrote | #1 |
| Changed in plainbox-provider-checkbox: | |
| assignee: | nobody → Yuan-Chen Cheng (ycheng-twn) |
| status: | New → Incomplete |
| importance: | Undecided → Medium |
Revision history for this message
| Yuan-Chen Cheng (ycheng-twn) wrote | #2 |
| Changed in plainbox-provider-checkbox: | |
| assignee: | Yuan-Chen Cheng (ycheng-twn) → Sylvain Pineau (sylvain-pineau) |
| Changed in oem-priority: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Yuan-Chen Cheng (ycheng-twn) |
| status: | New → Confirmed |
| Changed in plainbox-provider-checkbox: | |
| status: | Incomplete → New |
Revision history for this message
| Maksim Beliaev (beliaev-maksim) wrote | #3 |
| Changed in plainbox-provider-checkbox: | |
| status: | New → Expired |
To post a comment you must log in.
Could you please attach the output of `udevadm info -e`. It will help to fix the udev parser