1571606 - Perma Tier 2 fission devtools/client/webconsole/test/mochitest/browser_webconsole_websocket.js | Test timed out -

Status: RESOLVED FIXED

(DevTools :: Console, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: rgurzau [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=260009209&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/bmM-GaXhSGWAO0-GGQpyTQ/runs/0/artifacts/public/logs/live_backing.log

---

[task 2019-08-05T23:24:00.544Z] 23:24:00 INFO - TEST-START | devtools/client/webconsole/test/mochitest/browser_webconsole_websocket.js
[task 2019-08-05T23:24:00.583Z] 23:24:00 INFO - GECKO(8012) | [Parent 2308, Gecko_IOThread] WARNING: file z:/build/build/src/ipc/chromium/src/base/process_util_win.cc, line 160
[task 2019-08-05T23:24:45.577Z] 23:24:45 INFO - TEST-INFO | started process screenshot
[task 2019-08-05T23:24:45.636Z] 23:24:45 INFO - TEST-INFO | screenshot: exit 0
[task 2019-08-05T23:24:45.636Z] 23:24:45 INFO - Buffered messages logged at 23:24:00
[task 2019-08-05T23:24:45.636Z] 23:24:45 INFO - Entering test bound
[task 2019-08-05T23:24:45.636Z] 23:24:45 INFO - Adding a new tab with URL: data:text/html;charset=utf-8,Web Console test for bug 603750: Web Socket errors
[task 2019-08-05T23:24:45.636Z] 23:24:45 INFO - Console message: [JavaScript Error: "uncaught exception: Object" {file: "resource://testing-common/PromiseTestUtils.jsm" line: 112}]
[task 2019-08-05T23:24:45.636Z] 23:24:45 INFO - Tab added and finished loading
[task 2019-08-05T23:24:45.637Z] 23:24:45 INFO - Opening the toolbox
[task 2019-08-05T23:24:45.637Z] 23:24:45 INFO - Toolbox opened and focused
[task 2019-08-05T23:24:45.637Z] 23:24:45 INFO - Buffered messages logged at 23:24:01
[task 2019-08-05T23:24:45.637Z] 23:24:45 INFO - Console message: [JavaScript Error: "Firefox can’t establish a connection to the server at ws://0.0.0.0:81/." {file: "http://example.com/browser/devtools/client/webconsole/test/mochitest/test-websocket.js" line: 9}]
[task 2019-08-05T23:24:45.637Z] 23:24:45 INFO - Console message: [JavaScript Error: "Firefox can’t establish a connection to the server at ws://0.0.0.0:82/." {file: "http://example.com/browser/devtools/client/webconsole/test/mochitest/test-websocket.js" line: 15}]
[task 2019-08-05T23:24:45.637Z] 23:24:45 INFO - Buffered messages finished
[task 2019-08-05T23:24:45.637Z] 23:24:45 INFO - TEST-UNEXPECTED-FAIL | devtools/client/webconsole/test/mochitest/browser_webconsole_websocket.js | Test timed out -
[task 2019-08-05T23:24:46.176Z] 23:24:46 INFO - Removing tab.
[task 2019-08-05T23:24:46.176Z] 23:24:46 INFO - Waiting for event: 'TabClose' on [object XULElement].
[task 2019-08-05T23:24:46.186Z] 23:24:46 INFO - Got event: 'TabClose' on [object XULElement].
[task 2019-08-05T23:24:46.204Z] 23:24:46 INFO - Tab removed and finished closing
[task 2019-08-05T23:24:46.243Z] 23:24:46 INFO - GECKO(8012) | [Parent 2308, Gecko_IOThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 341
[task 2019-08-05T23:24:46.243Z] 23:24:46 INFO - TEST-UNEXPECTED-PASS | devtools/client/webconsole/test/mochitest/browser_webconsole_websocket.js | We expect at least one assertion to fail because this test file is marked as fail-if in the manifest. -
[task 2019-08-05T23:24:46.243Z] 23:24:46 INFO - TEST-INFO | expected FAIL
[task 2019-08-05T23:24:46.274Z] 23:24:46 INFO - GECKO(8012) | MEMORY STAT | vsize 2105208MB | vsizeMaxContiguous 65513259MB | residentFast 657MB | heapAllocated 184MB
[task 2019-08-05T23:24:46.274Z] 23:24:46 INFO - TEST-OK | devtools/client/webconsole/test/mochitest/browser_webconsole_websocket.js | took 45729ms
[task 2019-08-05T23:24:46.292Z] 23:24:46 INFO - checking window state
[task 2019-08-05T23:24:46.302Z] 23:24:46 INFO - GECKO(8012) | JavaScript error: resource://testing-common/PromiseTestUtils.jsm, line 112: uncaught exception: Object
[task 2019-08-05T23:24:46.302Z] 23:24:46 INFO - GECKO(8012) | [Child 5504, Chrome_ChildThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 341
[task 2019-08-05T23:24:46.303Z] 23:24:46 INFO - GECKO(8012) | [Child 5504, Chrome_ChildThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 341

Comment 1

[Intermittent Failures Robot]

20 failures in 553 pushes (0.036 failures/push) were associated with this bug yesterday.

Repository breakdown:

• mozilla-central: 20

Platform breakdown:

• linux64: 9
• windows10-64: 11

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1571606&startday=2019-08-05&endday=2019-08-05&tree=all

Comment 2

[Alexandru Michis [:malexandru]]

https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&tochange=8437b860258fe0a83da254761f7c8f5b221f7116&fromchange=9c91b33629b6e33de140b602361bbd27d686128a&searchStr=fission%2Cdt4

Nicolas, any thoughts on this?

Comment 3

[Nicolas Chevobbe [:nchevobbe]]

I'm seeing these 2 logs:

INFO - Console message: [JavaScript Error: "Firefox can’t establish a connection to the server at ws://0.0.0.0:81/." {file: "http://example.com/browser/devtools/client/webconsole/test/mochitest/test-websocket.js" line: 9}]
INFO - Console message: [JavaScript Error: "Firefox can’t establish a connection to the server at ws://0.0.0.0:82/." {file: "http://example.com/browser/devtools/client/webconsole/test/mochitest/test-websocket.js" line: 15}]

I'm not familiar with this test, but I can look at how this is supposed to work.

Comment 4

[Nicolas Chevobbe [:nchevobbe]]

is there a simple way to run tests with fission? or do I simply need to set fission.autostart to true and run them?

just saw --enable-fission in ./mach mochitest

Comment 5

[Nicolas Chevobbe [:nchevobbe]]

so I talked too fast: we do want the error messages to show up.
I have trouble understanding what's going on as the screenshot of the failure do show the messages.
So are we timing out because we're waiting for a test failure (because the test is annotated with fail-if = fission)?

Comment 6

[Alexandru Michis [:malexandru]]

I though so, but the line that mentions "fail-if = fission" in the manifest https://searchfox.org/mozilla-central/source/devtools/client/webconsole/test/mochitest/browser.ini#476 hasn't changed in that push.

I believe something changed and made it unexpectedly pass.

Comment 7

[Alexandru Michis [:malexandru]]

Perhaps one way to solve this would be to just delete that expectation?

Comment 8

[Nicolas Chevobbe [:nchevobbe]]

I do think so.
Should I take care of this?

Comment 9

[Alexandru Michis [:malexandru]]

I've made a try push to test this: https://treeherder.mozilla.org/#/jobs?repo=try&revision=0360e2e60e95010e8b4be01f9b8ba7bbae1d25eb

Comment 10

[Andreea Pavel [:apavel]]

(In reply to Nicolas Chevobbe [:nchevobbe] from comment #8)

I do think so.
Should I take care of this?

This has currently 46 failures in the last 2 days, which means that in ~2 more days it will reach the disable queue. If you can and have the time, yes, please work on fixing this.

Comment 11

[Intermittent Failures Robot]

31 failures in 858 pushes (0.036 failures/push) were associated with this bug yesterday.

Repository breakdown:

• mozilla-central: 31

Platform breakdown:

• linux64: 16
• windows10-64: 14
• linux64-shippable: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1571606&startday=2019-08-06&endday=2019-08-06&tree=all

Comment 12

[Nicolas Chevobbe [:nchevobbe]]

Let's see if this can help: https://treeherder.mozilla.org/#/jobs?repo=try&revision=784d047b46650d756a5a8a4dc428a7535e48fa37

Comment 13

[Nicolas Chevobbe [:nchevobbe]]

Attachment: Bug 1571606 - Fix browser_webconsole_websocket intermittent. r=Honza.

The test was navigating to a data url but it doesn't seem like it
was needed in the first place, as we only want to check that the
error messages are shown in the console input.
We also bump up the interval a bit just to be sure to capture the messages.

Comment 14

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/2b65be7d6779
Fix browser_webconsole_websocket intermittent. r=Honza.

Comment 15

[Stefan Hindli [:stefan_hindli]]

https://hg.mozilla.org/mozilla-central/rev/2b65be7d6779

Comment 17

[Intermittent Failures Robot]

55 failures in 4666 pushes (0.012 failures/push) were associated with this bug in the last 7 days.

This is the #30 most frequent failure this week.

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:

• mozilla-central: 55

Platform breakdown:

• linux64: 27
• windows10-64: 27
• linux64-shippable: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1571606&startday=2019-08-05&endday=2019-08-11&tree=all

Comment 18

[Chris Peterson [:cpeterson]]

Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission 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