Closed Bug 1767684 Opened 2 years ago Closed 2 years ago

Intermittent devtools/client/inspector/rules/test/browser_rules_cycle-angle.js | single tracking bug

Categories

(DevTools :: Inspector: Rules, defect, P3)

Product:
DevTools
Component:
Inspector: Rules
Type:
defect

Tracking

(firefox104 fixed)

Status:
RESOLVED FIXED
Milestone:
104 Branch
Tracking Flags:
Tracking Status
firefox104 --- fixed

People

(Reporter: jmaher, Assigned: jdescottes)

References

Details

(Keywords: intermittent-failure, intermittent-testcase, Whiteboard: [stockwell unknown])

Attachments

(2 files)

Bug 1767684 - [devtools] Use dedicated node instead of body in browser_rules_cycle-angle.js
(deleted), text/x-phabricator-request
Details
Bug 1767684 - [devtools] Skip browser_rules_cycle-angle.js on linux
(deleted), text/x-phabricator-request
Details
No description provided.

Filter on devtools-intermittent-singletrackingbug-triage

Severity: -- → S4
50 errors with:
10:12:28     INFO - TEST-UNEXPECTED-FAIL | devtools/client/inspector/rules/test/browser_rules_cycle-angle.js | Uncaught exception in test - at chrome://mochitests/content/browser/devtools/client/inspector/rules/test/browser_rules_cycle-angle.js:23 - TypeError: can't access property "valueSpan", getRuleViewProperty(...) is undefined

  linux1804-64-qr/opt-mochitest-devtools-chrome-fis: 5
  linux1804-64-qr/opt-mochitest-devtools-chrome-dt-no-eft-nofis: 17
  linux1804-64-qr/opt-mochitest-devtools-chrome-spi-nw-fis: 6
  linux1804-64-qr/opt-mochitest-devtools-chrome-a11y-checks-fis: 7
  linux1804-64-asan-qr/opt-mochitest-devtools-chrome-nofis: 3
  linux1804-64-qr/opt-mochitest-devtools-chrome-a11y-checks-nofis: 3
  linux1804-64-shippable-qr/opt-mochitest-devtools-chrome-fis: 2
  linux1804-64-asan-qr/opt-mochitest-devtools-chrome-fis: 1
  linux1804-64-shippable-qr/opt-mochitest-devtools-chrome-spi-nw-nofis: 1
  linux1804-64-qr/opt-mochitest-devtools-chrome-spi-nw-nofis: 3
  linux1804-64-shippable-qr/opt-mochitest-devtools-chrome-a11y-checks-fis: 1
  windows10-64-2004-asan-qr/opt-mochitest-devtools-chrome-fis: 1

There have been 44 total failures in the last 7 days, recent failure log.
Affected platforms are:

  • linux1804-64-asan-qr
  • linux1804-64-qr
  • linux1804-64-shippable-qr
[task 2022-06-28T22:15:05.866Z] 22:15:05     INFO - TEST-START | devtools/client/inspector/rules/test/browser_rules_cycle-angle.js
[task 2022-06-28T22:15:06.768Z] 22:15:06     INFO - TEST-INFO | started process screentopng
[task 2022-06-28T22:15:07.137Z] 22:15:07     INFO - TEST-INFO | screentopng: exit 0
[task 2022-06-28T22:15:07.138Z] 22:15:07     INFO - Buffered messages logged at 22:15:05
[task 2022-06-28T22:15:07.139Z] 22:15:07     INFO - Entering test bound 
[task 2022-06-28T22:15:07.141Z] 22:15:07     INFO - Adding a new tab with URL: data:text/html;charset=utf-8,%0A%20%20%3Cstyle%20type%3D%22text%2Fcss%22%3E%0A%20%20%20%20body%20%7B%0A%20%20%20%20%20%20filter%3A%20hue-rotate(1turn)%3B%0A%20%20%20%20%7D%0A%20%20%20%20div%20%7B%0A%20%20%20%20%20%20filter%3A%20hue-rotate(180deg)%3B%0A%20%20%20%20%7D%0A%20%20%3C%2Fstyle%3E%0A%20%20%3Cbody%3E%3Cdiv%3ETest%3C%2Fdiv%3Ecycling%20angle%20units%20in%20the%20rule%20view!%3C%2Fbody%3E%0A
[task 2022-06-28T22:15:07.142Z] 22:15:07     INFO - Buffered messages logged at 22:15:06
[task 2022-06-28T22:15:07.144Z] 22:15:07     INFO - Console message: [JavaScript Warning: "This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”." {file: "data:text/html;charset=utf-8,%0A%20%20%3Cstyle%20type%3D%22text%2Fcss%22%3E%0A%20%20%20%20body%20%7B%0A%20%20%20%20%20%20filter%3A%20hue-rotate(1turn)%3B%0A%20%20%20%20%7D%0A%20%20%20%20div%20%7B%0A%20%20%20%20%20%20filter%3A%20hue-rotate(180deg)%3B%0A%20%20%20%20%7D%0A%20%20%3C%2Fstyle%3E%0A%20%20%3Cbody%3E%3Cdiv%3ETest%3C%2Fdiv%3Ecycling%20angle%20units%20in%20the%20rule%20view!%3C%2Fbody%3E%0A" line: 0}]
[task 2022-06-28T22:15:07.144Z] 22:15:07     INFO - Tab added and finished loading
[task 2022-06-28T22:15:07.144Z] 22:15:07     INFO - Opening the inspector
[task 2022-06-28T22:15:07.146Z] 22:15:07     INFO - Opening the toolbox
[task 2022-06-28T22:15:07.148Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.149Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.150Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 62}]
[task 2022-06-28T22:15:07.151Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.152Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.153Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 62}]
[task 2022-06-28T22:15:07.154Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.155Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.156Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 62}]
[task 2022-06-28T22:15:07.156Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.157Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.158Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 62}]
[task 2022-06-28T22:15:07.159Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.160Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 511}]
[task 2022-06-28T22:15:07.160Z] 22:15:07     INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome" line: 62}]
[task 2022-06-28T22:15:07.160Z] 22:15:07     INFO - Toolbox opened and focused
[task 2022-06-28T22:15:07.161Z] 22:15:07     INFO - Buffered messages finished
[task 2022-06-28T22:15:07.162Z] 22:15:07     INFO - TEST-UNEXPECTED-FAIL | devtools/client/inspector/rules/test/browser_rules_cycle-angle.js | Uncaught exception in test - at chrome://mochitests/content/browser/devtools/client/inspector/rules/test/browser_rules_cycle-angle.js:23 - TypeError: can't access property "valueSpan", getRuleViewProperty(...) is undefined
[task 2022-06-28T22:15:07.162Z] 22:15:07     INFO - Stack trace:
[task 2022-06-28T22:15:07.162Z] 22:15:07     INFO - @chrome://mochitests/content/browser/devtools/client/inspector/rules/test/browser_rules_cycle-angle.js:23:40
[task 2022-06-28T22:15:07.163Z] 22:15:07     INFO - Async*handleTask@chrome://mochikit/content/browser-test.js:989:26
[task 2022-06-28T22:15:07.164Z] 22:15:07     INFO - _runTaskBasedTest@chrome://mochikit/content/browser-test.js:1061:18
[task 2022-06-28T22:15:07.164Z] 22:15:07     INFO - Tester_execTest@chrome://mochikit/content/browser-test.js:1196:14
[task 2022-06-28T22:15:07.165Z] 22:15:07     INFO - nextTest/<@chrome://mochikit/content/browser-test.js:978:14
[task 2022-06-28T22:15:07.166Z] 22:15:07     INFO - SimpleTest.waitForFocus/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:1041:13
[task 2022-06-28T22:15:07.166Z] 22:15:07     INFO - Leaving test bound 
[task 2022-06-28T22:15:07.167Z] 22:15:07     INFO - GECKO(3383) | console.log: "[DISPATCH] action type:" "CLEAR_FLEXBOX"
[task 2022-06-28T22:15:07.168Z] 22:15:07     INFO - GECKO(3383) | console.warn: "Async method failed in safeAsyncMethod" (new Error("Connection closed, pending request to server0.conn0.windowGlobal8589934625/layout32, type getGrids failed\n\nRequest stack:\nrequest@resource://devtools/shared/protocol/Front.js:293:14\ngenerateRequestMethods/</frontProto[name]@resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:49:19\ngetAllGrids@resource://devtools/client/fronts/layout.js:171:17\nexports.safeAsyncMethod/<@resource://devtools/shared/async-utils.js:61:25\ngetGrids@resource://devtools/client/inspector/grids/grid-inspector.js:449:35\nasync*_updateGridPanel@resource://devtools/client/inspector/grids/grid-inspector.js:320:35\nupdateGridPanel@resource://devtools/client/inspector/grids/grid-inspector.js:310:18\nonSidebarSelect@resource://devtools/client/inspector/grids/grid-inspector.js:639:10\n_emit@resource://devtools/shared/event-emitter.js:242:32\nemit@resource://devtools/shared/event-emitter.js:186:18\nemit@resource://devtools/shared/event-emitter.js:330:18\nhandleSelectionChange@resource://devtools/client/inspector/toolsidebar.js:216:10\naddAllQueuedTabs/<@resource://devtools/client/shared/components/tabs/TabBar.js:182:20\ncallCallback@resource://devtools/client/shared/vendor/react-dom.js:12127:12\ncommitUpdateEffects@resource://devtools/client/shared/vendor/react-dom.js:12166:19\ncommitUpdateQueue@resource://devtools/client/shared/vendor/react-dom.js:12154:22\ncommitLifeCycles@resource://devtools/client/shared/vendor/react-dom.js:12964:28\ncommitAllLifeCycles@resource://devtools/client/shared/vendor/react-dom.js:14174:23\ncommitRoot@resource://devtools/client/shared/vendor/react-dom.js:14380:28\ncompleteRoot/<@resource://devtools/client/shared/vendor/react-dom.js:15731:15\nunstable_runWithPriority@resource://devtools/client/shared/vendor/react.js:617:12\ncompleteRoot@resource://devtools/client/shared/vendor/react-dom.js:15730:27\nperformWorkOnRoot@resource://devtools/client/shared/vendor/react-dom.js:15659:21\nperformWork@resource://devtools/client/shared/vendor/react-dom.js:15567:24\nperformSyncWork@resource://devtools/client/shared/vendor/react-dom.js:15541:14\nrequestWork@resource://devtools/client/shared/vendor/react-dom.js:15410:5\nscheduleWork@resource://devtools/client/shared/vendor/react-dom.js:15224:16\nenqueueSetState@resource://devtools/client/shared/vendor/react-dom.js:8192:17\nComponent.prototype.setState@resource://devtools/client/shared/vendor/react.js:328:16\naddAllQueuedTabs@resource://devtools/client/shared/components/tabs/TabBar.js:180:10\naddAllQueuedTabs@resource://devtools/client/inspector/toolsidebar.js:78:18\nsetupSidebar@resource://devtools/client/inspector/inspector.js:1262:18\ninit@resource://devtools/client/inspector/inspector.js:234:10\nasync*open@resource://devtools/client/inspector/panel.js:12:28\nonLoad@resource://devtools/client/framework/toolbox.js:2610:27\n", "resource://devtools/shared/protocol/Front.js", 107))
[task 2022-06-28T22:15:07.255Z] 22:15:07     INFO - Removing tab.
[task 2022-06-28T22:15:07.255Z] 22:15:07     INFO - Waiting for event: 'TabClose' on [object XULElement].
[task 2022-06-28T22:15:07.272Z] 22:15:07     INFO - Got event: 'TabClose' on [object XULElement].
[task 2022-06-28T22:15:07.293Z] 22:15:07     INFO - Tab removed and finished closing
[task 2022-06-28T22:15:07.315Z] 22:15:07     INFO - GECKO(3383) | JavaScript error: , line 0: NotFoundError: No such JSWindowActor 'DevToolsFrame'
[task 2022-06-28T22:15:07.334Z] 22:15:07     INFO - Console message: [JavaScript Error: "NotFoundError: No such JSWindowActor 'DevToolsFrame'"]
[task 2022-06-28T22:15:07.338Z] 22:15:07     INFO - TEST-PASS | devtools/client/inspector/rules/test/browser_rules_cycle-angle.js | The main process DevToolsServer has no pending connection when the test ends -
Whiteboard: [stockwell needswork:owner]
Flags: needinfo?(jdescottes)

Not entirely clear why using the body fails sometimes on linux, but adding a first step of selecting a node is more inline with what other tests do, and
fixes the intermittent for me

Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Flags: needinfo?(jdescottes)
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8aa66a3b9067
[devtools] Use dedicated node instead of body in browser_rules_cycle-angle.js r=Honza

https://hg.mozilla.org/mozilla-central/rev/8aa66a3b9067

Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox104: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch

Can you take another look ?
This appeared https://treeherder.mozilla.org/logviewer?job_id=382949629&repo=autoland&lineNumber=25505

Thank you!

Flags: needinfo?(jdescottes)

Interesting, so it seems like we have a very similar failure, again quite frequent.
I am surprised because on try there was a clear improvement with the patch (https://treeherder.mozilla.org/jobs?repo=try&revision=0c73dfcd3f9ae57733e1aea88f2f80f4605ba082 -> 0/20 failures, vs https://treeherder.mozilla.org/jobs?repo=try&revision=27bee6ff314ac79054310243284ab94208ef3c26 7/20 failures).

I suggest we reopen and monitor the frequency. It's odd that the fix had such a drastic impact on test-verify but wouldn't help with the overall intermittent. I would still expect the frequency to drop. And at that point, I imagine that the remaining failure only occurs when the full suite runs.

This is still failing: https://treeherder.mozilla.org/logviewer?job_id=383035053&repo=autoland&lineNumber=24911

Reopened as per Julian's suggestion in Comment 16.

Status: RESOLVED → REOPENED
status-firefox104: fixed → ---
Resolution: FIXED → ---
Target Milestone: 104 Branch → ---

I checked that skipping the test does not move the intermittent to the next test.
I am not sure what makes this test problematic, I suppose this has to do with initializing widgets in the inspector to handler filters.
Let's skip this on linux for now.

https://hg.mozilla.org/mozilla-central/rev/a3bc429f351d

Status: REOPENED → RESOLVED
Closed: 2 years ago → 2 years ago
status-firefox104: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch
Flags: needinfo?(jdescottes)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: