1600194 - ubuntu1804 - toolkit/content/tests/chrome/test_bug624329.xhtml | Test timed out.

Status: NEW

(Toolkit :: UI Widgets, defect, P5)

Description

[Treeherder Bug Filer]

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

---

suite: mochitest-chrome-1proc
chunk: 2

context:
[task 2019-11-28T21:19:35.222Z] 21:19:35 INFO - TEST-START | toolkit/content/tests/chrome/test_bug624329.xhtml
[task 2019-11-28T21:19:35.286Z] 21:19:35 INFO - GECKO(7298) | JavaScript error: resource://specialpowers/SpecialPowersParent.jsm, line 580: TypeError: this.manager.rootFrameLoader is null
[task 2019-11-28T21:19:35.287Z] 21:19:35 INFO - GECKO(7298) | JavaScript error: , line 0: NS_ERROR_UNEXPECTED:
[task 2019-11-28T21:19:55.276Z] 21:19:55 INFO - Not taking screenshot here: see the one that was previously logged
[task 2019-11-28T21:19:55.277Z] 21:19:55 INFO - Buffered messages logged at 21:19:35
[task 2019-11-28T21:19:55.277Z] 21:19:55 INFO - must wait for load
[task 2019-11-28T21:19:55.277Z] 21:19:55 INFO - must wait for focus
[task 2019-11-28T21:19:55.277Z] 21:19:55 INFO - Buffered messages finished
[task 2019-11-28T21:19:55.278Z] 21:19:55 INFO - TEST-UNEXPECTED-FAIL | toolkit/content/tests/chrome/test_bug624329.xhtml | Test timed out.
[task 2019-11-28T21:19:55.278Z] 21:19:55 INFO - SimpleTest.ok@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:277:18
[task 2019-11-28T21:19:55.278Z] 21:19:55 INFO - openTestWindow/timeoutID<@chrome://mochitests/content/chrome/toolkit/content/tests/chrome/test_bug624329.xhtml:34:11
[task 2019-11-28T21:19:55.278Z] 21:19:55 INFO - setTimeout handler*SimpleTest_setTimeoutShim@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:686:43
[task 2019-11-28T21:19:55.278Z] 21:19:55 INFO - openTestWindow@chrome://mochitests/content/chrome/toolkit/content/tests/chrome/test_bug624329.xhtml:33:17
[task 2019-11-28T21:19:55.279Z] 21:19:55 INFO - onload@chrome://mochitests/content/chrome/toolkit/content/tests/chrome/test_bug624329.xhtml:1:1
[task 2019-11-28T21:19:56.279Z] 21:19:56 INFO - GECKO(7298) | MEMORY STAT | vsize 2981MB | residentFast 326MB | heapAllocated 117MB
[task 2019-11-28T21:19:56.297Z] 21:19:56 INFO - TEST-OK | toolkit/content/tests/chrome/test_bug624329.xhtml | took 21060ms

Comment 1

[Edwin Takahashi (:egao | infrequent contributor)]

This test is part of a series of failures that all have the same error message from SpecialPoewrsParent.jsm, specifically this portion:

GECKO(7298) | JavaScript error: resource://specialpowers/SpecialPowersParent.jsm, line 580: TypeError: this.manager.rootFrameLoader is null
GECKO(7298) | JavaScript error: , line 0: NS_ERROR_UNEXPECTED:

The other bugs that have the same lines are in the see also section. I will not tag the triage owners for this bug as it is possible that fixing one of those will render all other bugs fixed.

Comment 2

[Intermittent Failures Robot]

1 failures in 4331 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• try: 1

Platform breakdown:

• linux64: 1

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

Comment 3

[Edwin Takahashi (:egao | infrequent contributor)]

I wonder if all of these are related to the base marionette issue with window placement and sizing as documented in bug 1600391.

Comment 4

[Edwin Takahashi (:egao | infrequent contributor)]

:bgrins - I was not able to pinpoint the cause of this permafail on ubuntu1804.

This test permanently fails on all variants of linux when run with ubuntu1804. Here is a more recent try run:
https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&selectedJob=283879357&tier=1%2C2%2C3&author=egao%40mozilla.com&fromchange=18c600bbfd6776a1f5601e0a4fec1405e08b7481&searchStr=mochitest-chrome%2C1

Could you please redirect the ni to someone that may be able to take a look?

To run tests using ubuntu1804, please use mach try fuzzy --ubuntu-bionic and select linux64 mochitest-chrome-1proc as normal.

Comment 5

[Brian Grinstead [:bgrins]]

Looks like this is related to context menu positioning. Given that this is on ubuntu1804 I'm wondering if this is similar to the panel bugs Neil just fixed which had to do with the system theme size changing (like Bug 1602620). Neil, would you mind taking a look at this one too?

Comment 6

[Neil Deakin]

The test times out trying to call win.maximize() on a dialog. The dialog when opened does not have a maximize button. Perhaps the window manager isn't honouring the request for a maximize button?

Anyway, this looks like a gtk/window manager issue and not related to the context menu.

Comment 7

[Edwin Takahashi (:egao | infrequent contributor)]

Perhaps it would be the case that this behavior is relying on a specific behavior in compiz used by the ubuntu1604 test image.

What is the path forward? The window manager for ubuntu1804 is GNOME desktop and this will not be changed according to decisions made in bug 1601828. Mochitest suites are the only significant tests that have not yet been migrated to run on ubuntu1804.

Would it be acceptable to mark this test with a fail-if for ubuntu1804?

Comment 8

[Edwin Takahashi (:egao | infrequent contributor)]

This bug and bug 1602626 are blocking the migration of mochitest-chrome-1proc suites to run under ubuntu1804.

For context, window manager has been changed in ubuntu1804 to GNOME from the legacy compiz that was used in the ubuntu1604 test image. I have found this change to be directly responsible for a handful of failures - such as bug 1600176.
However, it was agreed by the stakeholders that adapting the image to accommodate tests that make assumptions in the test behavior is not an ideal path forward, hence returning to compiz is off the table.

Neil, could you please take a look at why this test times out under GNOME?

Comment 9

[Neil Deakin]

I think I already did above. The test is waiting for the window to be maximized but the dialog box cannot be maximized. Someone more familiar with gtk would be better equipped to work further on this bug.

Comment 10

[Edwin Takahashi (:egao | infrequent contributor)]

Attachment: Bug 1600194 - mark test_bug624329.xhtml as expected failure on ubuntu1804

Comment 11

[Edwin Takahashi (:egao | infrequent contributor)]

This test has been disabled in the following patch due to lack of movement: https://phabricator.services.mozilla.com/D60612

Comment 12

[Mark Striemer [:mstriemer]]

Leaving this open if the discussion is useful later, but doesn't seem like a high priority