Changes in mochitest chunking made test_peerConnection_basicH264Video.html permafail on Gecko 37/38 on Windows

RESOLVED WORKSFORME

Status

()

Core
WebRTC
--
blocker
RESOLVED WORKSFORME
3 years ago
3 years ago

People

(Reporter: RyanVM, Unassigned)

Tracking

Trunk
x86
Windows 8.1
Points:
---
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(firefox37 wontfix, firefox38 fixed, firefox38.0.5 fixed, firefox39 unaffected, firefox40 unaffected, firefox-esr38 fixed)

Details

(Reporter)

Description

3 years ago
Today I uplifted bug 1143218 to Aurora and Beta to fix mochitest-gl (it had been running in both mochitest-plain and mochitest-gl and was also permafailing on Android 4.0 due to mozharness changes). As a result of this landing, test_peerConnection_basicH264Video.html is now perma-timeout on Windows 8 on both Aurora38 and Beta37.

Looking at the before and after logs, the difference appears to be the tests/dom/media/test directory moving from the end of mochitest-2 to the beginning of mochitest-3.

Given the upcoming merge, this is very urgent. We need to fix or disable the test ASAP.
Flags: needinfo?(rjesup)
(Reporter)

Comment 2

3 years ago
Correction, this is happening across all Windows versions.
Summary: Changes in mochitest chunking made test_peerConnection_basicH264Video.html permafail on Gecko 37/38 on Windows 8 → Changes in mochitest chunking made test_peerConnection_basicH264Video.html permafail on Gecko 37/38 on Windows
I'll look at this ASAP, thanks.

Is there an easy to to invoke the same set of tests as would occur in mochitest-2?  (also, I'm confused, as at least as of a week or two ago all the dom/media/tests/mochitest tests ran in m3 on desktop.)
Flags: needinfo?(rjesup) → needinfo?(ryanvm)
Also the example was a PGO build; I presume this affects non-PGO as well?
(Reporter)

Comment 5

3 years ago
All opt builds on aurora/beta are PGO. Interestingly, on Aurora it appears to affect opt and debug, but on Beta, it only affects debug.

I believe that mach supports the --total-chunks=5, --this-chunk=3 lingo, so that should work locally.
Flags: needinfo?(ryanvm)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
(Reporter)

Comment 25

3 years ago
Skipped on 38.
https://hg.mozilla.org/releases/mozilla-aurora/rev/9b7464221b8a
Assignee: nobody → ryanvm
status-firefox38: --- → fixed
(Reporter)

Comment 26

3 years ago
Good one, mcMerge.
Assignee: ryanvm → nobody
status-firefox37: --- → disabled
status-firefox38: fixed → disabled
status-firefox39: --- → unaffected
(Reporter)

Comment 27

3 years ago
Try says this is green on 38 again. Yay.
https://hg.mozilla.org/releases/mozilla-release/rev/a2843f37ba38
Assignee: nobody → ryanvm
Flags: in-testsuite+
(Reporter)

Updated

3 years ago
Assignee: ryanvm → nobody
Status: NEW → RESOLVED
Last Resolved: 3 years ago
status-firefox37: disabled → wontfix
status-firefox38: disabled → fixed
status-firefox38.0.5: --- → affected
status-firefox40: --- → unaffected
status-firefox-esr38: --- → affected
Resolution: --- → WORKSFORME
(Reporter)

Comment 28

3 years ago
https://hg.mozilla.org/releases/mozilla-esr38/rev/a2843f37ba38
Assignee: nobody → ryanvm
status-firefox-esr38: affected → fixed
(Reporter)

Comment 29

3 years ago
https://hg.mozilla.org/releases/mozilla-beta/rev/a2843f37ba38
status-firefox38.0.5: affected → fixed
(Reporter)

Updated

3 years ago
Assignee: ryanvm → nobody
You need to log in before you can comment on or make changes to this bug.