Closed
Bug 845452
Opened 12 years ago
Closed 12 years ago
Lower volume of media mochitest tests
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla22
People
(Reporter: whimboo, Assigned: whimboo)
Details
Attachments
(1 file)
1.25 KB,
patch
|
roc
:
review+
ted
:
review+
|
Details | Diff | Splinter Review |
As it came up on bug 837458 and by a full testrun on my own machine which blew me away the ears, we should mute the media mochitests if possible:
>(In reply to Henrik Skupin (:whimboo) from comment #21)
>> Clint, I run all the media mochitests lately and none of the media tests
>> muted audio. Not sure why that is but lets ask Roc if we should follow-up on
>> that separately.
>
>Yes I think we should.
>
>Ideally the test machines would be muted at the system level somehow.
Muting at the system level will only work for our test machines but not if you have to run the tests on your own machine while you want keep e.g. other music running. It's really distracting.
Comment 1•12 years ago
|
||
Given that the code paths followed for full-mute might reasonably be different from with normal volume, I don't think muting is a good idea. 10% volume, or some suitably small fraction that doesn't kill volume entirely, seems like the right thing to do. Perhaps a volume-scaling pref set during test runs (defaulting to 1.0 otherwise) would be a reasonable way to do this.
We already have media.volume_scale. Just set that.
Comment 3•12 years ago
|
||
(In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #2)
> We already have media.volume_scale. Just set that.
Back over to Core::WebRTC then. We could just add a simple one line patch to head.js runTest to set this pref.
For those of us who don't know the pref - what value would we set it to? "0.0"?
Component: Mochitest → WebRTC: Audio/Video
Product: Testing → Core
QA Contact: jsmith
Version: unspecified → Trunk
Assignee | ||
Comment 4•12 years ago
|
||
Not sure why you moved that to WebRTC. This is a bug covering all media tests and has to rely as initially filed in the Mochitest component. Moving back so we might want to get this addressed as a default preference set by the framework.
Component: WebRTC: Audio/Video → Mochitest
Product: Core → Testing
QA Contact: jsmith
Comment 5•12 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #4)
> Not sure why you moved that to WebRTC. This is a bug covering all media
> tests and has to rely as initially filed in the Mochitest component. Moving
> back so we might want to get this addressed as a default preference set by
> the framework.
Didn't realize you were targeting all mochitests originally when I wrote that comment.
(In reply to Jason Smith [:jsmith] from comment #3)
> For those of us who don't know the pref - what value would we set it to?
> "0.0"?
Just to be on the safe side (i.e. make sure we don't take any shortcut codepaths that hide bugs), I'd set it to 0.01 or something like that.
Assignee | ||
Updated•12 years ago
|
Summary: Mute media mochitest tests → Lower volume of media mochitest tests
Assignee | ||
Comment 7•12 years ago
|
||
This patch implements what has been suggested in that bug. We do not completely silence the tests but scale the volume down. '0.01' seems to be a good candidate here. Asking for review from roc for the media tests, and ted for the build system.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Attachment #723700 -
Flags: review?(ted)
Attachment #723700 -
Flags: review?(roc)
Comment 8•12 years ago
|
||
Just for safety, we might want to get a try run here just to make sure nothing blows up setting this pref.
Assignee | ||
Comment 9•12 years ago
|
||
A try run has already been submitted but I missed to add this to my last comment: https://tbpl.mozilla.org/?tree=Try&rev=ee22a32a8461
Attachment #723700 -
Flags: review?(roc) → review+
Updated•12 years ago
|
Attachment #723700 -
Flags: review?(ted) → review+
Assignee | ||
Comment 10•12 years ago
|
||
Target Milestone: --- → mozilla22
Comment 11•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•