Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Gecko Bug 1457129] Correct WebRTC getStats WPT to wait for remote stats before comparing #13942

Merged
merged 1 commit into from
Nov 12, 2018

Conversation

moz-wptsync-bot
Copy link
Collaborator

If care is not taken to wait for remote stats on senders and receivers, then the contents
of the stats reports will not be stable. Waiting for this stability should fix our
intermittent failures checking that RTCRtpSender/Receiver.getStats() returns the
same dictionaries that RTCPeerConnection.getStats(sender/receiver.track) does.

Differential Revision: https://phabricator.services.mozilla.com/D5804

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1457129
gecko-commit: 0874b793fc046bf31ca80c673d5dfa0bb38ea343
gecko-integration-branch: autoland
gecko-reviewers: jib

If care is not taken to wait for remote stats on senders and receivers, then the contents
of the stats reports will not be stable. Waiting for this stability should fix our
intermittent failures checking that RTCRtpSender/Receiver.getStats() returns the
same dictionaries that RTCPeerConnection.getStats(sender/receiver.track) does.

Differential Revision: https://phabricator.services.mozilla.com/D5804

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1457129
gecko-commit: 0874b793fc046bf31ca80c673d5dfa0bb38ea343
gecko-integration-branch: autoland
gecko-reviewers: jib
Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already reviewed downstream.

@sideshowbarker
Copy link
Contributor

w3c-test:mirror

@jgraham
Copy link
Contributor

jgraham commented Nov 7, 2018

This seems to be unstable in gecko. Since it landed in m-c I'm minded to merge the PR anyway, but it would be good to understand what's going on here (due to the amount of output, the taskcluster stability job — which is currently set to always succeed — has the more useful information on what was unstable).

@jgraham jgraham merged commit 42392b1 into master Nov 12, 2018
@moz-wptsync-bot moz-wptsync-bot deleted the gecko/1457129 branch November 12, 2018 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants