Closed Bug 1596333 Opened 6 years ago Closed 6 years ago

Intermittent Tier 2 Fission browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | Test timed out -

Categories

(Firefox :: Settings UI, defect, P5)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1605006

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure)

Filed by: btara [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=276117436&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/fHmqwRepQoa4rh1old3vuA/runs/0/artifacts/public/logs/live_backing.log


....
[task 2019-11-14T01:23:56.402Z] 01:23:56 INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | connection window closed -
[task 2019-11-14T01:23:56.402Z] 01:23:56 INFO - 192: testWithProperties: waiting for any of uri and mode prefs to change
[task 2019-11-14T01:23:56.402Z] 01:23:56 INFO - 192: testWithProperties: prefs changed
[task 2019-11-14T01:23:56.402Z] 01:23:56 INFO - 192: testWithProperties: fin
[task 2019-11-14T01:23:56.402Z] 01:23:56 INFO - Leaving test bound testVariation
[task 2019-11-14T01:23:56.402Z] 01:23:56 INFO - Entering test bound testVariation
[task 2019-11-14T01:23:56.402Z] 01:23:56 INFO - starting test: toggle mode on
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - 2: testWithProperties: testing with {"name":"toggle mode on","clickMode":true,"expectedModeValue":2,"expectedUriValue":"","expectedFinalUriPref":"https://mozilla.cloudflare-dns.com/dns-query"}
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | Check the proper URL is loaded -
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | Element should not be null, when checking visibility -
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | Overlay is visible -
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - found chrome://browser/skin/preferences/preferences.css
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - found chrome://global/skin/in-content/common.css
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - found chrome://browser/skin/preferences/in-content/preferences.css
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - found chrome://browser/skin/preferences/in-content/dialog.css
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | All expectedStyleSheetURLs should have been found -
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | connection window opened -
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - 147: testWithProperties: connections dialog now open
[task 2019-11-14T01:23:56.403Z] 01:23:56 INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | URI textbox has expected value -
[task 2019-11-14T01:23:56.404Z] 01:23:56 INFO - 147: testWithProperties: clickMode, waiting for the pref observer
[task 2019-11-14T01:23:56.404Z] 01:23:56 INFO - 147: testWithProperties: clickMode, pref changed
[task 2019-11-14T01:23:56.404Z] 01:23:56 INFO - 152: testWithProperties: clickMode, mouse click synthesized
[task 2019-11-14T01:23:56.404Z] 01:23:56 INFO - 152: testWithProperties: calling acceptDialog
[task 2019-11-14T01:23:56.404Z] 01:23:56 INFO - 167: testWithProperties: waiting for the dialogClosingPromise
[task 2019-11-14T01:23:56.404Z] 01:23:56 INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | connection window closed -
[task 2019-11-14T01:23:56.404Z] 01:23:56 INFO - 171: testWithProperties: waiting for any of uri and mode prefs to change
[task 2019-11-14T01:23:56.405Z] 01:23:56 INFO - Buffered messages finished
[task 2019-11-14T01:23:56.405Z] 01:23:56 INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | Test timed out -
[task 2019-11-14T01:23:56.405Z] 01:23:56 INFO - GECKO(7700) | MEMORY STAT | vsize 2104634MB | vsizeMaxContiguous 65994238MB | residentFast 408MB | heapAllocated 103MB
[task 2019-11-14T01:23:56.405Z] 01:23:56 INFO - TEST-OK | browser/components/preferences/in-content/tests/browser_connection_dnsoverhttps.js | took 45122ms

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?

Blocks Fission mochitests milestone (M4.1)

Fission Milestone: ? → M4.1

Blake, this bug is a blocker for Fission's current milestone (M4.1 aka "fix all the mochitests"), but it's currently unassigned and a priority P5. How should I mark this bug so your team will re-triage it? If you don't think this mochitest failure should block shipping Fission, just let me know.

Flags: needinfo?(bwinton)
See Also: → 1605006

I think this looks like a dupe of bug 1605006, which is also a non-Fission intermittent.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE

To answer Chris's question, needinfo-ing me is probably fine, at least until Jaws gets back and starts triaging again. 🙂

Flags: needinfo?(bwinton)
Fission Milestone: M4.1 → ---
You need to log in before you can comment on or make changes to this bug.