Perma [tier2] browser/base/content/test/protectionsUI/browser_protectionsUI_cookies_subview.js | No contentBlockingEvent events should be received - Got 1, expected undefined
Categories
(Firefox :: Protections UI, defect, P5)
Tracking
()
People
(Reporter: intermittent-bug-filer, Assigned: dimi)
References
(Regression)
Details
(Keywords: intermittent-failure, regression, Whiteboard: [retriggered])
Attachments
(2 files)
Filed by: csabou [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=296967064&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/e8BgDbplQGO_dvuFrixEdQ/runs/0/artifacts/public/logs/live_backing.log
[task 2020-04-09T13:50:29.187Z] 13:50:29 INFO - TEST-PASS | browser/base/content/test/protectionsUI/browser_protectionsUI_cookies_subview.js | Main view was shown -
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - Console message: [JavaScript Warning: "Request to access cookie or storage on “https://test1.example.org/browser/browser/base/content/test/protectionsUI/cookieServer.sjs” was blocked because we are blocking all third-party storage access requests and content blocking is enabled."]
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - Console message: [JavaScript Warning: "Request to access cookie or storage on “https://test1.example.org/browser/browser/base/content/test/protectionsUI/cookieServer.sjs” was blocked because we are blocking all third-party storage access requests and content blocking is enabled."]
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - Buffered messages logged at 13:50:29
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - Console message: [JavaScript Warning: "Request to access cookie or storage on “https://test1.example.org/browser/browser/base/content/test/protectionsUI/cookieServer.sjs” was blocked because we are blocking all third-party storage access requests and content blocking is enabled."]
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - Console message: [JavaScript Error: "The character encoding of the plain text 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 file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature." {file: "https://test1.example.org/browser/browser/base/content/test/protectionsUI/cookieServer.sjs" line: 0}]
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - Received onContentBlockingEvent event: 2147786880 (1 of 1)
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - Buffered messages finished
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/protectionsUI/browser_protectionsUI_cookies_subview.js | No contentBlockingEvent events should be received - Got 1, expected undefined
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - Stack trace:
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - chrome://mochikit/content/browser-test.js:test_is:1320
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - chrome://mochitests/content/browser/browser/base/content/test/protectionsUI/browser_protectionsUI_cookies_subview.js:assertSitesListed:160
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - chrome://mochitests/content/browser/browser/base/content/test/protectionsUI/browser_protectionsUI_cookies_subview.js:testCookiesSubView:268
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1062
[task 2020-04-09T13:50:29.188Z] 13:50:29 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1097
[task 2020-04-09T13:50:29.189Z] 13:50:29 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:925
[task 2020-04-09T13:50:29.189Z] 13:50:29 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:918
[task 2020-04-09T13:50:29.355Z] 13:50:29 INFO - TEST-PASS | browser/base/content/test/protectionsUI/browser_protectionsUI_cookies_subview.js | Cookies view was shown -
Comment 1•5 years ago
|
||
Dimi, Tim, we've been getting a bunch of Fission perma failure bugs filed for anti-tracking tests (also bug 1628501 and bug 1628514). I suspect this is related to your work, can you take a look? :)
Thanks!
Assignee | ||
Comment 2•5 years ago
|
||
I'll check those bugs.
Updated•5 years ago
|
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 6•5 years ago
|
||
I haven't figured out the root case.
This seems to only happen in windows opt build. This is quite strange based on what we've changed.
For some reason, in the windows build, it triggers additional anti-tracking checks and generates a content blocking event, which we don't expect receiving that in the test case[1].
Before Bug 1624552, this additional event was not notified because we couldn't get the top-level window, however, after Bug 1624552, getting the top-level window is no longer necessary, hence the event was notified.
I kind of feel that this is happening because we are doing the right thing now, but I am not sure, will keep investigate.
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 8•5 years ago
|
||
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 11•5 years ago
|
||
Following tests are disabled
- browser_protectionsUI_cookies_subview.js
- browser_protectionsUI_state.js
- browser_allowListNotifications.js
- browser_urlDecorationStripping.js
The reason that this tests are failing in fission mode is because in
window64 opt mode, additional content blocking event is triggered when
loading chrome:://global/skin/icons/resizer.svg
We don't have this problem before because in this case, we couldn't get the
top-level window, so the event was not fired.
But the recent working to make anti-tracking fission compatible (Bug 1624552) removes
the need of getting top-level window, so the event is fired and
testcases don't expect that.
Comment 12•5 years ago
|
||
Obviously, this content blocking event is triggered when loading a chrome resource. Does it make sense to trigger blocking events for chrome resources? Maybe we can filter out this and not notify an event in this case.
Assignee | ||
Comment 13•5 years ago
|
||
(In reply to Tim Huang[:timhuang] from comment #12)
Obviously, this content blocking event is triggered when loading a chrome resource. Does it make sense to trigger blocking events for chrome resources? Maybe we can filter out this and not notify an event in this case.
Yes, I think that is one of the possible solution we can do.
I have test this
https://treeherder.mozilla.org/#/jobs?repo=try&revision=4219f846d8d049e00baa0f3ca188af6e405138e3
2 out of the 4 testcases can be fixed by the way you suggested, and then I found out there are still 2 testcases needed to be fixed.
I haven't checked what the root cause for the other two, I'll check it and see what is the best solution.
Assignee | ||
Updated•5 years ago
|
Comment 14•5 years ago
|
||
Comment 15•5 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 17•5 years ago
|
||
Comment hidden (Intermittent Failures Robot) |
Comment 19•5 years ago
|
||
Comment 20•5 years ago
|
||
bugherder |
Assignee | ||
Comment 21•4 years ago
|
||
no failure with the correct fix, close this bug
Description
•