The work mentioned in Bug 1149374 seems to be necessary but perhaps not sufficient to get these tests running. Affected tests: test_peerConnection_basicH264Video.html test_peerConnection_bug1042791.html test_peerConnection_scaleResolution.html (uses both VP8 and H.264, VP8 works) There may be more affected tests, I'll add them there as I find them.

dminor: FYI, These tests will be part of the new Mdm2 tests I am adding in Bug 1353509. I did an initial try run where they were enabled, and you can see the results at: https://treeherder.allizom.org/#/jobs?repo=try&revision=18eafb2b0e186e6f05ffbacdf097d3d64179d2cc&filter-searchStr=Mdm2

I tried a quick rebase of the patches at Bug 1267141 and running test_peerConnection_basicH264Video.html. It still fails.

I think there are probably some misunderstanding here. These three webrtc/peerconection tests are not related to bug 1149374 or 1267141, which are for EME API. May I know why we change the skip-if comment here? https://hg.mozilla.org/integration/mozilla-inbound/rev/bba81310ba7b The original comment should be correct: H.264 should be present in the SDP offer - didn't expect -1, but got it, many other failures

(In reply to Munro Mengjue Chiang [:mchiang] from comment #3) > I think there are probably some misunderstanding here. > These three webrtc/peerconection tests are not related to bug 1149374 or > 1267141, which are for EME API. > > May I know why we change the skip-if comment here? > https://hg.mozilla.org/integration/mozilla-inbound/rev/bba81310ba7b > > The original comment should be correct: > H.264 should be present in the SDP offer - didn't expect -1, but got it, > many other failures The reason I changed the comment was to have a bug to track getting these tests enabled. I guess I misinterpreted the work in Bug 1043403 as making it possible for the fake H.264 implementation to work on B2G and thought we had to do something similar for Android. At any rate, that manifest is going to be removed any day now. Once that is done, I'll update any H.264 related failures to point to this bug, rather than Bug 1149374.

FYI, I ran these tests against my local devices using the soon to be available manifests from bug 1358118 https://treeherder.allizom.org/#/jobs?repo=try&revision=18185e3acf6c06af05b11953f7970331e12babb9&selectedJob=87058128

Mass change P2->P3 to align with new Mozilla triage process.