Tests skipped in 'toolkit/components/antitracking/test/browser/browser.ini' for new Fission platform triage
Categories
(Core :: Privacy: Anti-Tracking, task, P3)
Tracking
()
| Fission Milestone | Future |
People
(Reporter: ahal, Unassigned)
References
Details
(Whiteboard: [fxatps-query-stripping])
The following tests were disabled in toolkit/components/antitracking/test/browser/browser.ini due to new Fission platform triage:
browser_urlQueryStringStripping.js
Full diff:
--- a/toolkit/components/antitracking/test/browser/browser.ini
+++ b/toolkit/components/antitracking/test/browser/browser.ini
@@ -135,16 +135,18 @@ support-files = matchAll.js
support-files = sharedWorker.js partitionedSharedWorker.js
[browser_PBMCookieBehavior.js]
[browser_socialtracking.js]
[browser_socialtracking_save_image.js]
[browser_thirdPartyStorageRejectionForCORS.js]
[browser_urlDecorationStripping.js]
tags = remote-settings
[browser_urlQueryStringStripping.js]
+skip-if =
+ fission && os == "linux" && asan # New platform triage
support-files = file_stripping.html
[browser_staticPartition_cache.js]
support-files =
!/browser/components/originattributes/test/browser/file_cache.html
!/browser/components/originattributes/test/browser/file_thirdPartyChild.audio.ogg
!/browser/components/originattributes/test/browser/file_thirdPartyChild.embed.png
!/browser/components/originattributes/test/browser/file_thirdPartyChild.fetch.html
!/browser/components/originattributes/test/browser/file_thirdPartyChild.iframe.html
See the following try push for failures:
https://treeherder.mozilla.org/jobs?repo=try&revision=ad7a18fdad3b8e35b44152c16d94babb80387cd8
To run these failures in your own try push, first revert the skip-if
annotations, then run:
$ ./mach try fuzzy --rebuild 3 toolkit/components/antitracking/test/browser/browser.ini
Then use the fuzzy interface to select the task(s) which are relevant to the
removed skip-if expression(s). Please note the failure may be intermittent
and/or been fixed since the triage took place.
Comment 1•4 years ago
|
||
We need to determine whether this browser-chrome test failure should block shipping Fission. Tracking for Fission Milestone M7a for the initial audit. Then we can decide whether to move this bug to Fission M8 or post-MVP (Fission Future).
Here is a recent Try run for Fission browser-chrome:
https://treeherder.mozilla.org/jobs?repo=try&revision=ad7a18fdad3b8e35b44152c16d94babb80387cd8
Comment 2•4 years ago
|
||
This test suite is currently being fully skipped on asan/tasn due to https://bugzilla.mozilla.org/show_bug.cgi?id=1662229, so I don't think we can do much about this particular test.
Comment 3•4 years ago
|
||
(In reply to Nika Layzell [:nika] (ni? for response) from comment #2)
This test suite is currently being fully skipped on asan/tasn due to https://bugzilla.mozilla.org/show_bug.cgi?id=1662229, so I don't think we can do much about this particular test.
In that case, I don't think this bug needs to block Fission M7a.
@ Tim, we can probably just remove this new Fission annotation and see what happens after Linux asan bug 1662229 is fixed.
[browser_urlQueryStringStripping.js]
skip-if =
fission && os == "linux" && asan # Bug 1713909 - new Fission platform triage
Comment 4•4 years ago
|
||
Currently, the query stripping is just a prototype that is even disabled in Nightly. So I agree with that it doesn't block Fission.
(In reply to Chris Peterson [:cpeterson] from comment #3)
@ Tim, we can probably just remove this new Fission annotation and see what happens after Linux asan bug 1662229 is fixed.
LGTM
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 5•3 years ago
|
||
This is specifically fission and linux and asan so shouldn't block us from releasing.
Description
•