Bug 928188 - Audio test should specifies device when play and record sample sound
Summary: Audio test should specifies device when play and record sample sound
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Test Suite (tests)
Version: 1.6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Qian Cai
QA Contact: Qian Cai
URL:
Whiteboard:
Depends On:
Blocks: 928202 969013
TreeView+ depends on / blocked
 
Reported: 2013-03-27 05:40 UTC by Yunlong Xue
Modified: 2013-08-06 17:48 UTC (History)
4 users (show)

Fixed In Version: hwcert-client-1.6.4-R44
Clone Of:
: 928202 1929211 (view as bug list)
Environment:
Last Closed: 2013-08-06 17:48:53 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1139 0 normal SHIPPED_LIVE hwcert-client-1.6 bug fix and enhancement update 2013-08-06 21:42:43 UTC

Description Yunlong Xue 2013-03-27 05:40:35 UTC 
If a system have multi soundcards/devices, such as 
/devices/pci0000:00/0000:00:03.0/sound/card0 and
/devices/pci0000:00/0000:00:1b.0/sound/card1

And default playback and capture devices are on card0.

In this situation, both following tests will use card0 to play and record sample sound, so card1 is never tested.
v7 run --test=audio --udi=/devices/pci0000:00/0000:00:03.0/sound/card0
v7 run --test=audio --udi=/devices/pci0000:00/0000:00:1b.0/sound/card1

I think we'd better set default or specify device when play and rec, such as:
"aplay /usr/share/sounds/alsa/Front_Center.wav -D plughw:0"
(Not sure how to us sox :P )
Comment 1 Yunlong Xue 2013-03-27 05:43:01 UTC 
Or at least, print some info in log to show which device were used to play and rec.
Comment 9 Lingzhu Xiang 2013-06-25 09:11:16 UTC 
Verified in hwcert-client-1.6.4-56.el6
Comment 13 errata-xmlrpc 2013-08-06 17:48:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1139.html
Note You need to log in before you can comment on or make changes to this bug.