webrtc web-platform-tests need a cleanup
Categories
(Core :: WebRTC: Signaling, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox79 | --- | fixed |
People
(Reporter: bwc, Assigned: bwc)
References
Details
Attachments
(8 files)
|
47 bytes,
text/x-phabricator-request
|
Details | Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review |
There are lots of disabled webrtc wpt, with no bug numbers in the ini files. The ini files need to be evaluated, tests re-enabled if possible, and bug links added if not.
| Assignee | ||
Comment 1•5 years ago
|
||
| Assignee | ||
Comment 2•5 years ago
|
||
Seeing lots of instances of bug 1641788 in that push.
| Assignee | ||
Comment 3•5 years ago
|
||
| Assignee | ||
Comment 4•5 years ago
|
||
| Assignee | ||
Comment 5•5 years ago
|
||
| Assignee | ||
Comment 6•5 years ago
•
|
||
Push without fuzzy --full: Only seeing known intermittents. https://treeherder.mozilla.org/#/jobs?repo=try&revision=fd392d1975c6e8ac19e8d77cc984d24fb4ae2ac9
Push with fuzzy --full: Mostly known intermittents here, but there are some failures on android that I don't see in bugzilla anywhere: https://treeherder.mozilla.org/#/jobs?repo=try&revision=d1edc0bf860fc9a0e8bc43812e5b31c7e777e5a1
Here's a push on the base revision to check out those Android failures: https://treeherder.mozilla.org/#/jobs?repo=try&revision=32debcb7d02700c2c724ac230492a103488e42d6
| Assignee | ||
Comment 7•5 years ago
•
|
||
The failures on fuzzy --full android happen on the base revision too. So, try looks good. Let's see if that holds up after a rebase!
| Assignee | ||
Comment 8•5 years ago
•
|
||
| Assignee | ||
Comment 9•5 years ago
|
||
| Assignee | ||
Comment 10•5 years ago
|
||
Depends on D79527
| Assignee | ||
Comment 11•5 years ago
|
||
Depends on D79528
| Assignee | ||
Comment 12•5 years ago
|
||
Depends on D79529
| Assignee | ||
Comment 13•5 years ago
|
||
Depends on D79530
| Assignee | ||
Comment 14•5 years ago
|
||
Depends on D79531
| Assignee | ||
Comment 15•5 years ago
|
||
Try looks good.
| Assignee | ||
Comment 16•5 years ago
•
|
||
| Assignee | ||
Comment 17•5 years ago
|
||
Lots of bug 1645663 in those pushes. Also seeing some intermittents that bug 1645219 fixes.
| Assignee | ||
Comment 18•5 years ago
•
|
||
| Assignee | ||
Comment 19•5 years ago
•
|
||
| Assignee | ||
Comment 20•5 years ago
|
||
| Assignee | ||
Comment 21•5 years ago
|
||
Comment 22•5 years ago
|
||
Comment 25•5 years ago
|
||
Backed out 6 changesets (bug 1643058) for WPT failures in webrtc/RTCRtpReceiver-getSynchronizationSources.https.html. CLOSED TREE
Log:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=307330485&repo=autoland&lineNumber=11620
Push with failure:
https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&revision=6dd69c93d9e2a9f06e7404f4655207adf6a22fdd
Backout:
https://hg.mozilla.org/integration/autoland/rev/8245e9943d9de53b9f3a3a3193704b9b4d49400f
| Assignee | ||
Comment 27•5 years ago
|
||
Yeah, the merge was bad. Trying again...
| Assignee | ||
Comment 28•5 years ago
|
||
| Assignee | ||
Comment 29•5 years ago
•
|
||
| Assignee | ||
Comment 30•5 years ago
|
||
| Assignee | ||
Comment 31•5 years ago
|
||
| Assignee | ||
Comment 32•5 years ago
|
||
Depends on D79532
| Assignee | ||
Comment 33•5 years ago
|
||
Depends on D80947
Comment 34•5 years ago
|
||
| Assignee | ||
Comment 36•5 years ago
|
||
/webrtc/RTCPeerConnection-createDataChannel.html seems to be having unexpected errors on Chrome, but the only change there was marking the test as long.
/webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html is the same story.
/webrtc/datachannel-emptystring.html just had some necessary cleanup added.
/webrtc/no-media-call.html just had some necessary cleanup added.
Looks like Chrome needs to update their test expectations.
Comment 37•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/ebad65f70e2d
https://hg.mozilla.org/mozilla-central/rev/b32e18c3d542
https://hg.mozilla.org/mozilla-central/rev/4767df198c29
https://hg.mozilla.org/mozilla-central/rev/cf062b9c00b4
https://hg.mozilla.org/mozilla-central/rev/9c677d996512
https://hg.mozilla.org/mozilla-central/rev/141ade17eb3c
https://hg.mozilla.org/mozilla-central/rev/36f54439ad2e
https://hg.mozilla.org/mozilla-central/rev/78d7201bf2a0
Description
•