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

Split iceGatheringState tests into separate files & update expectations #24797

Merged
merged 1 commit into from Aug 3, 2020

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Jul 29, 2020

This allows us to run more tests than if we mark a single file as
timing out. Important to ensure we don't cause regressions when rolling
https://webrtc-review.googlesource.com/c/src/+/180481 into chromium.

TBR since I am just moving things around and want to unblock a reland

TBR=hta@chromium.org

Bug: chromium:1110833, chromium:1071733
Change-Id: Ib9f9cefe3fd89d764495a41a66422f191761df62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2324251
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792650}

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.

The review process for this patch is being conducted in the Chromium project.

This allows us to run more tests than if we mark a single file as
timing out. Important to ensure we don't cause regressions when rolling
https://webrtc-review.googlesource.com/c/src/+/180481 into chromium.

# TBR since I am just moving things around and want to unblock a reland
TBR=hta@chromium.org

Bug: chromium:1110833, chromium:1071733
Change-Id: Ib9f9cefe3fd89d764495a41a66422f191761df62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2324251
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792650}
@LukeZielinski
Copy link
Contributor

Firefox failure is due to a slow test approaching timeout limit
Chrome dev failure is due to flake in a test that was not modified in this change:

Unstable results

Test Subtest Results Messages
/webrtc/protocol/crypto-suite.https.html OK: 9/10, TIMEOUT: 1/10
/webrtc/protocol/crypto-suite.https.html tlsVersion is acceptable on video-only PASS: 9/10, TIMEOUT: 1/10 Test timed out
/webrtc/protocol/crypto-suite.https.html dtlsCipher is acceptable on data-only NOTRUN: 1/10, PASS: 9/10
/webrtc/protocol/crypto-suite.https.html dtlsCipher is acceptable on video-only NOTRUN: 1/10, PASS: 9/10
/webrtc/protocol/crypto-suite.https.html srtpCipher is acceptable on data-only NOTRUN: 1/10, PASS: 9/10
/webrtc/protocol/crypto-suite.https.html srtpCipher is acceptable on video-only NOTRUN: 1/10, PASS: 9/10
/webrtc/protocol/crypto-suite.https.html tlsGroup is acceptable on data-only FAIL: 9/10, NOTRUN: 1/10 assert_true: Value present: expected true got false
/webrtc/protocol/crypto-suite.https.html tlsGroup is acceptable on video-only FAIL: 9/10, NOTRUN: 1/10 assert_true: Value present: expected true got false

A helper file was changed so lots of tests got rerun, but code was only moved around so should be a no-op. The flaky test above doesn't use any of the code that was modified in this CL. Also, can't reproduce the flake locally at ToT.

Retrying here, but will likely force-merge this.

@LukeZielinski LukeZielinski reopened this Jul 30, 2020
@LukeZielinski LukeZielinski reopened this Jul 31, 2020
@stephenmcgruer stephenmcgruer merged commit 76b44c0 into master Aug 3, 2020
@stephenmcgruer stephenmcgruer deleted the chromium-export-cl-2324251 branch August 3, 2020 14:07
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.

None yet

5 participants