1713888 - Tests skipped in 'browser/base/content/test/backforward/browser.ini' for new Fission platform triage

Status: RESOLVED FIXED

(Firefox :: General, task)

Description

[Andrew Halberstadt [:ahal]]

The following tests were disabled in browser/base/content/test/backforward/browser.ini due to new Fission platform triage:
browser_history_menu.js

Full diff:

diff --git a/browser/base/content/test/backforward/browser.ini b/browser/base/content/test/backforward/browser.ini
--- a/browser/base/content/test/backforward/browser.ini
+++ b/browser/base/content/test/backforward/browser.ini
@@ -1,1 +4,3 @@
 [browser_history_menu.js]
+skip-if =
+  fission && (os != "linux" || asan)  # New platform triage

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 browser/base/content/test/backforward/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

[Chris Peterson [:cpeterson]]

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

[Nika Layzell [:nika] (ni? for response)]

I don't see an instance of this failure in the linked try push. Can we get more information about what the failure looks like?

Comment 3

[Andrew Halberstadt [:ahal]]

Yes, sorry about that. I realized after the fact that there was a bug in Push Health that may have caused me to think certain tasks were more intermittent than they really were. So it's possible I skipped this thinking it was more frequent than it was in reality. Also this bug was filed via script, so I didn't manually verify that the try push captured failures in each bug being filed (I've made some tweaks to the script already for next time, thanks for bearing with me).

I made this push to try and reproduce the failure:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=f5f92bf57a92c6dcc0f68c25a42a0f64f1975887

If it's green enough we can use this bug to remove the annotation.

Comment 4

[Andrew Halberstadt [:ahal]]

Attachment: Bug 1713888 - Remove 'skip-if' annotation in browser/base/content/test/backforward/browser_history_menu.js, r?jmaher!

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/30c66b8fb21c
Remove 'skip-if' annotation in browser/base/content/test/backforward/browser_history_menu.js, r=jmaher

Comment 6

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/30c66b8fb21c