Closed Bug 1390001 Opened 3 years ago Closed 2 years ago
_webconsole _allow _mixedcontent _securityerrors .js is going to permafail on Win8 when Gecko 57 merges to Beta on 2017-09-20
[Tracking Requested - why for this release]: Permafailing test on the next merge day. I have no idea why this only affects Win8 runs, but it hit consistently across two different pushes :(. Can you please take a look and/or pass this along to someone for more investigation, Ryan? Thanks! https://treeherder.mozilla.org/logviewer.html#?job_id=122815648&repo=try TEST-UNEXPECTED-FAIL | devtools/client/webconsole/test/browser_webconsole_allow_mixedcontent_securityerrors.js | Test timed out - TEST-UNEXPECTED-FAIL | devtools/client/webconsole/test/browser_webconsole_allow_mixedcontent_securityerrors.js | failed to match rule: Logged mixed active content - TEST-UNEXPECTED-FAIL | devtools/client/webconsole/test/browser_webconsole_allow_mixedcontent_securityerrors.js | failed to match rule: Logged mixed passive content - image -
Passing this on to Brian who currently works on the console.
Flags: needinfo?(jryans) → needinfo?(bgrinstead)
Priority: -- → P2
Component: Developer Tools → Developer Tools: Console
browser_webconsole_block_mixedcontent_securityerrors.js times out if browser_webconsole_allow_mixedcontent_securityerrors.js is skipped. https://treeherder.mozilla.org/logviewer.html#?job_id=123755402&repo=try
And skipping the "block" version just makes browser_webconsole_bug_752559_ineffective_iframe_sandbox_warning.js time out about 3/4 of the time. I really don't know what's going on with this one :(
I've been using this patch to work around the issues at the moment. If we can't find anybody to prioritize investigating these issues, I'd rather just land it on m-c so I can stop juggling it in my patch queue.
Attachment #8902457 - Flags: feedback?(pbrosset)
Comment on attachment 8902457 [details] [diff] [review] workaround patch Review of attachment 8902457 [details] [diff] [review]: ----------------------------------------------------------------- These are old front-end tests. We are nearly ready to ship the new front-end on all channels (currently enabled by default in nightly and dev-edition already). The new front-end has new tests. We eventually want to look at these older tests again and convert those that offer coverage we don't yet have to the new front-end. However in the meantime, spending time fixing difficult test failures in old tests isn't looking like it's going to be worth our time. So I'm fine disabling those. Thanks Ryan.
Attachment #8902457 - Flags: feedback?(pbrosset) → feedback+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/72b2e3517b04 Disable various webconsole tests on Win64 that permafail after the uplift to Beta. f=pbro, r=me
Thanks for the feedback, Patrick.
Let's see if this bug is still needed after all tests are moved to the new frontend (Bug 1400847)
Depends on: 1400847
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.