Perma [tier 2] toolkit/components/antitracking/test/browser/browser_allowListSeparationInPrivateAndNormalWindows.js | Some console message should be generated -
Categories
(Core :: Privacy: Anti-Tracking, defect, P1)
Tracking
()
Fission Milestone | M4.1 |
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: timhuang)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: intermittent-failure, regression, Whiteboard: [stockwell disabled])
Attachments
(1 file)
Filed by: ccoroiu [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=263954336&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/Zfx4uHpeQzSI9ZJpfiUW0w/runs/0/artifacts/public/logs/live_backing.log
task 2019-08-28T22:45:36.921Z] 22:45:36 INFO - TEST-START | toolkit/components/antitracking/test/browser/browser_allowListSeparationInPrivateAndNormalWindows.js
[task 2019-08-28T22:45:37.730Z] 22:45:37 INFO - TEST-INFO | started process screentopng
[task 2019-08-28T22:45:38.130Z] 22:45:38 INFO - TEST-INFO | screentopng: exit 0
[task 2019-08-28T22:45:38.131Z] 22:45:38 INFO - Buffered messages logged at 22:45:36
[task 2019-08-28T22:45:38.133Z] 22:45:38 INFO - Entering test bound
[task 2019-08-28T22:45:38.134Z] 22:45:38 INFO - Leaving test bound
[task 2019-08-28T22:45:38.135Z] 22:45:38 INFO - Entering test bound
[task 2019-08-28T22:45:38.137Z] 22:45:38 INFO - Starting blocking cookieBehavior (4) without allow list test Test that we don't honour a private allow list exception in a normal window running in a normal window with iframe sandbox set to null and access removal set to null
[task 2019-08-28T22:45:38.138Z] 22:45:38 INFO - TEST-PASS | toolkit/components/antitracking/test/browser/browser_allowListSeparationInPrivateAndNormalWindows.js | callbackAfterRemoval must be passed when accessRemoval is non-null -
[task 2019-08-28T22:45:38.139Z] 22:45:38 INFO - Buffered messages logged at 22:45:37
[task 2019-08-28T22:45:38.139Z] 22:45:38 INFO - Creating a new tab
[task 2019-08-28T22:45:38.141Z] 22:45:38 INFO - Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "http://example.net/browser/toolkit/components/antitracking/test/browser/page.html" line: 0}]
[task 2019-08-28T22:45:38.142Z] 22:45:38 INFO - Creating a 3rd party content
[task 2019-08-28T22:45:38.144Z] 22:45:38 INFO - Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "https://tracking.example.org/browser/toolkit/components/antitracking/test/browser/3rdParty.html" line: 0}]
[task 2019-08-28T22:45:38.145Z] 22:45:38 INFO - Sending code to the 3rd party content
[task 2019-08-28T22:45:38.146Z] 22:45:38 INFO - Buffered messages finished
[task 2019-08-28T22:45:38.147Z] 22:45:38 INFO - TEST-UNEXPECTED-FAIL | toolkit/components/antitracking/test/browser/browser_allowListSeparationInPrivateAndNormalWindows.js | Some console message should be generated -
[task 2019-08-28T22:45:38.147Z] 22:45:38 INFO - Stack trace:
[task 2019-08-28T22:45:38.148Z] 22:45:38 INFO - chrome://mochikit/content/browser-test.js:test_ok:1580
[task 2019-08-28T22:45:38.148Z] 22:45:38 INFO - chrome://mochitests/content/browser/toolkit/components/antitracking/test/browser/antitracking_head.js:_createTask/<:674
[task 2019-08-28T22:45:38.149Z] 22:45:38 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1350
[task 2019-08-28T22:45:38.150Z] 22:45:38 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1385
[task 2019-08-28T22:45:38.150Z] 22:45:38 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:1213
[task 2019-08-28T22:45:38.151Z] 22:45:38 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:805
[task 2019-08-28T22:45:38.153Z] 22:45:38 INFO - Not taking screenshot here: see the one that was previously logged
Comment 1•5 years ago
|
||
Comment 2•5 years ago
|
||
This looks to be from Bug 1540117: https://treeherder.mozilla.org/#/jobs?repo=autoland&selectedJob=264061728&searchStr=windows%2C10%2Cx64%2Cquantumrender%2Copt%2Cmochitests%2Cwith%2Cfission%2Cenabled%2Ctest-windows10-64-qr%2Fopt-mochitest-browser-chrome-fis-e10s-6%2Cm-fis%28bc6%29&tochange=1f918cd124a8ea37967bb35e0734795b1ef2c6c8&fromchange=1630fa8aa729c0c3689d7f42905ddaf1b10682aa
Ehsan, do you have the time to look into this?
Updated•5 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment 4•5 years ago
|
||
You can go ahead and disable this test, this module doesn't support Fission properly yet, this is something that bug 1576291 is on file for.
Updated•5 years ago
|
Pushed by rgurzau@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5882c5dd07f4
Disable browser_allowListSeparationInPrivateAndNormalWindows.js on fission. r=intermittent-reviewers,jmaher
Comment 6•5 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 9•5 years ago
|
||
bugherder uplift |
Updated•5 years ago
|
Comment 10•4 years ago
|
||
Baku, Wennie suggested I ask you about triaging this bug.
Should this mochitest failure block enabling Fission by default in Nightly? This bug is currently a P5. This browser_allowListSeparationInPrivateAndNormalWindows.js test is currently disabled in Fission mode (and also non-Fission os == "mac" && !debug
from bug 1503778). The Fission team hopes that other teams can fix their Fission mochitest failures before March so we can start testing Fission with more Nightly users soon.
Assignee | ||
Comment 12•4 years ago
|
||
Sorry for the late response,
I do think this should block the Fission by default in Nightly because of the failure is due to that the AntiTracking backend is not fission compatible. So, there will be many regressions if we enable Fission without bug 1576291. We are actively working on making this Fission compatible and targetting Nightly 77.
Assignee | ||
Comment 13•4 years ago
|
||
This test is currently enabled in Fission.
Updated•4 years ago
|
Updated•2 years ago
|
Description
•