Closed Bug 1667949 Opened 4 years ago Closed 3 years ago

TEST-UNEXPECTED-FAIL | comm/calendar/test/browser/eventDialog/browser_eventDialogModificationPrompt.js FAIL Uncaught exception - at resource://testing-common/mozmill/utils.jsm:127 - TimeoutError: Calendar:EventDialog did not load in time

Categories

(Calendar :: Calendar Frontend, defect)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ishikawa, Unassigned)

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

This may be related to a few other errors such as bug 1625671.

I build and test C-C TB locally under Debian GNU/Linux.
I noticed that there are new errors of the form

  FAIL Uncaught exception - at resource://testing-common/mozmill/utils.jsm:127 - TimeoutError: Calendar:EventDialog did not load in time

during local C-C TB mochitest.

I have not seen them in earlier local test logs (early September, for example).
It may be the error message is new, but I am not sure.

The stack trace from the log is shown below for
comm/calendar/test/browser/eventDialog/browser_eventDialogModificationPrompt.js
and
comm/calendar/test/browser/eventDialog/browser_utf8.js.

comm/calendar/test/browser/eventDialog/browser_eventDialogModificationPrompt.js
  FAIL Uncaught exception - at resource://testing-common/mozmill/utils.jsm:127 - TimeoutError: Calendar:EventDialog did not load in time
Stack trace:
TimeoutError@resource://testing-common/mozmill/utils.jsm:127:13
waitFor@resource://testing-common/mozmill/utils.jsm:183:11
MozMillController.prototype.waitFor@resource://testing-common/mozmill/controller.jsm:774:9
waitForEventDialogWindow@resource://testing-common/mozmill/CalendarUtils.jsm:443:16
execEventDialogCallback@resource://testing-common/mozmill/CalendarUtils.jsm:431:45
invokeNewEventDialog@resource://testing-common/mozmill/CalendarUtils.jsm:334:9
testEventDialogModificationPrompt@chrome://mochitests/content/browser/comm/calendar/test/browser/eventDialog/browser_eventDialogModificationPrompt.js:42:9
Tester_execTest/<@chrome://mochikit/content/browser-test.js:1069:34
Tester_execTest@chrome://mochikit/content/browser-test.js:1109:11
nextTest/<@chrome://mochikit/content/browser-test.js:932:14
SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:1037:23
  FAIL Uncaught exception - at resource://testing-common/mozmill/utils.jsm:127 - TimeoutError: Calendar:EventDialog did not load in time
Stack trace:
TimeoutError@resource://testing-common/mozmill/utils.jsm:127:13
waitFor@resource://testing-common/mozmill/utils.jsm:183:11
MozMillController.prototype.waitFor@resource://testing-common/mozmill/controller.jsm:774:9
waitForEventDialogWindow@resource://testing-common/mozmill/CalendarUtils.jsm:443:16
execEventDialogCallback@resource://testing-common/mozmill/CalendarUtils.jsm:431:45
invokeNewEventDialog@resource://testing-common/mozmill/CalendarUtils.jsm:334:9
testDescriptionWhitespace@chrome://mochitests/content/browser/comm/calendar/test/browser/eventDialog/browser_eventDialogModificationPrompt.js:90:11
Tester_execTest/<@chrome://mochikit/content/browser-test.js:1069:34
comm/calendar/test/browser/eventDialog/browser_utf8.js
  FAIL Uncaught exception - at resource://testing-common/mozmill/utils.jsm:127 - TimeoutError: Calendar:EventDialog did not load in time
Stack trace:
TimeoutError@resource://testing-common/mozmill/utils.jsm:127:13
waitFor@resource://testing-common/mozmill/utils.jsm:183:11
MozMillController.prototype.waitFor@resource://testing-common/mozmill/controller.jsm:774:9
waitForEventDialogWindow@resource://testing-common/mozmill/CalendarUtils.jsm:443:16
execEventDialogCallback@resource://testing-common/mozmill/CalendarUtils.jsm:431:45
invokeNewEventDialog@resource://testing-common/mozmill/CalendarUtils.jsm:334:9
testUTF8@chrome://mochitests/content/browser/comm/calendar/test/browser/eventDialog/browser_utf8.js:34:9
Tester_execTest/<@chrome://mochikit/content/browser-test.js:1069:34
Tester_execTest@chrome://mochikit/content/browser-test.js:1109:11
nextTest/<@chrome://mochikit/content/browser-test.js:932:14
SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:1037:23

The error may be timing-sensitive.
This is because I don't see it in other people's try-comm-central submission.
(I am running local Debian GNU/Linux image inside virtualbox running under windows 10.
The local PC has AMD Ryzen 2700 and 32GB of memory. VirtualBox is assigned 16 GB of memory.
It is reasonably fast.)

I am quoting the portion of the log from a submission of someone else in the next post for comparison purposes.

The error may be timing-sensitive.
This is because I don't see it in other people's try-comm-central submission.
(I am running local Debian GNU/Linux image inside virtualbox running under windows 10.
The local PC has AMD Ryzen 2700 and 32GB of memory. VirtualBox is assigned 16 GB of memory.
It is reasonably fast.)

I am quoting the portion of the log from a submissiof others in the next post.

For example, I am quoting the log from the job:
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=8c903ef8a06a2dfcbb64d4ce7fe1666adc0947ea
and the log.
https://firefoxci.taskcluster-artifacts.net/U-OqL-bgRYef9hL4fNFUrA/0/public/logs/live_backing.log

The tests for browser_eventDialogModificationPrompt.js and browser_utf8.js seem to pass on the tryserver without such timeout I see locally. However, I notice that there
are many errors during the tests, and the test took 99.3 seconds(!) and 17.9 seconds respectively on the tryserver, a tad too long to think it ran successfully without undue timing issue.

That is why I think there can be some hidden timing-dependent errors.

Oh, I have applied locally the patch from the Bug 1621274 that would streamline the execution by eliminating the unwanted backtrace from an assertion (there are too many of them).
So maybe my code may run a thread faster than stock C-C TB without the patch from bug 1621274.

Please use the standard title for filing such bugs, and add "intermittent-failure" so that treeherder knows to suggest the bug when starring the tree.
You can also easily file it that way directly from treeherder using the "file a bug" button.

Summary: C-C TB mochitest error. FAIL Uncaught exception - at resource://testing-common/mozmill/utils.jsm:127 - TimeoutError: Calendar:EventDialog did not load in time → TEST-UNEXPECTED-FAIL | comm/calendar/test/browser/eventDialog/browser_eventDialogModificationPrompt.js FAIL Uncaught exception - at resource://testing-common/mozmill/utils.jsm:127 - TimeoutError: Calendar:EventDialog did not load in time

(In reply to Magnus Melin [:mkmelin] from comment #2)

Please use the standard title for filing such bugs, and add "intermittent-failure" so that treeherder knows to suggest the bug when starring the tree.
You can also easily file it that way directly from treeherder using the "file a bug" button.

Yeah, I will do that when I realize that the same bugs are logged locally and remotely on the tryserver.

No failures for 2 months.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: