Intermittent test_audio_wakelock.html | There was at least 200 milliseconds between the stop and the wakelock release

RESOLVED FIXED in Firefox 24, Firefox OS v1.1hd

Status

()

Core
DOM: Device Interfaces
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: emorley, Assigned: kanru)

Tracking

({intermittent-failure})

Trunk
mozilla26
ARM
Android
intermittent-failure
Points:
---
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(firefox24 fixed, firefox25 fixed, firefox26 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 wontfix, b2g-v1.1hd fixed)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Android Tegra 250 mozilla-central opt test mochitest-2 on 2013-06-04 04:05:57 PDT for push 7e3a4ebcf067

slave: tegra-052

https://tbpl.mozilla.org/php/getParsedLog.php?id=23762781&tree=Mozilla-Central

{
6362 INFO TEST-START | /tests/content/html/content/test/test_audio_wakelock.html
6363 INFO TEST-PASS | /tests/content/html/content/test/test_audio_wakelock.html | Audio element locked the target == cpu
6364 INFO TEST-PASS | /tests/content/html/content/test/test_audio_wakelock.html | Audio element locked the cpu - no paused
6365 INFO TEST-PASS | /tests/content/html/content/test/test_audio_wakelock.html | Audio element locked the target == cpu
6366 INFO TEST-PASS | /tests/content/html/content/test/test_audio_wakelock.html | Audio element locked the cpu - no paused
6367 ERROR TEST-UNEXPECTED-FAIL | /tests/content/html/content/test/test_audio_wakelock.html | There was at least 200 milliseconds between the stop and the wakelock release
}
Created attachment 757961 [details] [diff] [review]
Patch, v1

I'm not sure whether the other test is OK; it depends on exactly when we fire
the progress event.  But I think this is the right change.
Attachment #757961 - Flags: review?(amarchesini)
test_video_wakelock already does what I have in this patch; we don't need to copy the change over there.
Attachment #757961 - Flags: review?(amarchesini) → review+
Is it possible to get this landed on b2g18?  It's a test-only change.
status-b2g18: --- → affected
https://hg.mozilla.org/mozilla-central/rev/1d4b4a57d890
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla24
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
See Also: → bug 881443
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: mozilla24 → ---
Comment hidden (Treeherder Robot)
https://hg.mozilla.org/integration/b2g-inbound/rev/29b159a4442e
Assignee: nobody → kchen
https://hg.mozilla.org/mozilla-central/rev/29b159a4442e
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
https://hg.mozilla.org/releases/mozilla-aurora/rev/63d366c0a224
https://hg.mozilla.org/releases/mozilla-beta/rev/3cf04822fc17
https://hg.mozilla.org/releases/mozilla-b2g18/rev/11e112d54f22
status-b2g18: affected → fixed
status-b2g18-v1.0.0: --- → wontfix
status-b2g18-v1.0.1: --- → wontfix
status-b2g-v1.1hd: --- → affected
status-firefox24: --- → fixed
status-firefox25: --- → fixed
status-firefox26: --- → fixed
https://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/11e112d54f22
status-b2g-v1.1hd: affected → fixed
You need to log in before you can comment on or make changes to this bug.