Closed Bug 1607867 Opened 4 years ago Closed 4 years ago

ubuntu1804 INTERMITTENT - TEST-UNEXPECTED-TIMEOUT | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | rejectionhandled is dispatched from a queued task, and not immediately - Test timed out

Categories

(Core :: DOM: Core & HTML, defect, P5)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1622348

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

Attachments

(1 file, 1 obsolete file)

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


suite: wpt
chunk: 12

notes: shippable opt fission

context:
[task 2020-01-07T00:34:11.665Z] 00:34:11 INFO - TEST-START | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html
[task 2020-01-07T00:34:11.666Z] 00:34:11 INFO - Closing window 8589934654
[task 2020-01-07T00:34:11.677Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 15: Error:
[task 2020-01-07T00:34:11.679Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 24: Error:
[task 2020-01-07T00:34:11.679Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 732: Error:
[task 2020-01-07T00:34:11.679Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 62: Error:
[task 2020-01-07T00:34:11.680Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 131: Error:
[task 2020-01-07T00:34:11.680Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 157: Error:
[task 2020-01-07T00:34:11.680Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 120: Error:
[task 2020-01-07T00:34:11.681Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 35: Error:
[task 2020-01-07T00:34:11.683Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 48: Error:
[task 2020-01-07T00:34:11.684Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 78: Error:
[task 2020-01-07T00:34:11.686Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 98: Error:
[task 2020-01-07T00:34:11.688Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 142: Error:
[task 2020-01-07T00:34:11.689Z] 00:34:11 INFO - PID 19263 | JavaScript error: , line 0: InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable
[task 2020-01-07T00:34:11.980Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 15: Error:
[task 2020-01-07T00:34:11.982Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 24: Error:
[task 2020-01-07T00:34:11.982Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 490: Error:
[task 2020-01-07T00:34:11.983Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 507: Error:
[task 2020-01-07T00:34:11.983Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 522: Error:
[task 2020-01-07T00:34:11.983Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 543: Error:
[task 2020-01-07T00:34:11.983Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 569: Error:
[task 2020-01-07T00:34:11.984Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 588: Error:
[task 2020-01-07T00:34:11.984Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 605: Error:
[task 2020-01-07T00:34:11.984Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 628: Error:
[task 2020-01-07T00:34:11.984Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 653: Error:
[task 2020-01-07T00:34:11.985Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 732: Error:
[task 2020-01-07T00:34:11.986Z] 00:34:11 INFO - PID 19263 | JavaScript error: , line 0: uncaught exception: undefined
[task 2020-01-07T00:34:11.988Z] 00:34:11 INFO - PID 19263 | JavaScript error: , line 0: uncaught exception: undefined
[task 2020-01-07T00:34:11.988Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 62: Error:
[task 2020-01-07T00:34:11.988Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 131: Error:
[task 2020-01-07T00:34:11.989Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 157: Error:
[task 2020-01-07T00:34:11.989Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 120: Error:
[task 2020-01-07T00:34:11.990Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 35: Error:
[task 2020-01-07T00:34:11.991Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 48: Error:
[task 2020-01-07T00:34:11.992Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 78: Error:
[task 2020-01-07T00:34:11.994Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 98: Error:
[task 2020-01-07T00:34:11.996Z] 00:34:11 INFO - PID 19263 | JavaScript error: http://web-platform.test:8000/html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/support/promise-rejection-events.js, line 142: Error:
[task 2020-01-07T00:34:11.997Z] 00:34:11 INFO - PID 19263 | JavaScript error: , line 0: InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable
[task 2020-01-07T00:34:12.001Z] 00:34:12 INFO - PID 19263 | JavaScript error: , line 0: uncaught exception: undefined
[task 2020-01-07T00:34:12.001Z] 00:34:12 INFO - PID 19263 | JavaScript error: , line 0: uncaught exception: undefined
[task 2020-01-07T00:34:22.014Z] 00:34:22 INFO -
[task 2020-01-07T00:34:22.014Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | delayed handling: queueTask after promise creation/rejection, plus many promise microtasks, is not too late to attach a rejection handler
[task 2020-01-07T00:34:22.014Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | delayed handling: a nested-task delay before attaching a handler causes unhandledrejection
[task 2020-01-07T00:34:22.015Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | delayed handling: a nested-queueTask after promise creation/rejection, plus promise microtasks, is too late to attach a rejection handler
[task 2020-01-07T00:34:22.015Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | delayed handling: a nested-queueTask before promise creation/rejection, plus many promise microtasks, is too late to attach a rejection handler
[task 2020-01-07T00:34:22.015Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | delayed handling: a nested-queueTask after promise creation/rejection, plus many promise microtasks, is too late to attach a rejection handler
[task 2020-01-07T00:34:22.016Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | delayed handling: delaying handling by setTimeout(,10) will cause both events to fire
[task 2020-01-07T00:34:22.017Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | delayed handling: delaying handling rejected promise created from createImageBitmap will cause both events to fire
[task 2020-01-07T00:34:22.018Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | mutationObserverMicrotask vs. queueTask ordering is not disturbed inside unhandledrejection events
[task 2020-01-07T00:34:22.019Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | queueTask ordering vs. the task queued for unhandled rejection notification (1)
[task 2020-01-07T00:34:22.019Z] 00:34:22 INFO - TEST-PASS | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | queueTask ordering vs. the task queued for unhandled rejection notification (2)
[task 2020-01-07T00:34:22.020Z] 00:34:22 INFO - TEST-UNEXPECTED-TIMEOUT | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | rejectionhandled is dispatched from a queued task, and not immediately - Test timed out
[task 2020-01-07T00:34:22.020Z] 00:34:22 INFO - TEST-UNEXPECTED-TIMEOUT | /html/webappapis/scripting/processing-model-2/unhandled-promise-rejections/promise-rejection-events.html | expected OK

:edgar - this is a low intermittence bug that I have observed on the ubuntu1804 test image for linux.

I see that there were two bugs, bug 1560511 and bug 1550290 in the past but that seemed like it was geared towards fennec and have since been closed.

The try push is here: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&tier=1%2C2%2C3&revision=7c42c7c9db6bf4d60eb457a287ee43207ce52780

As seen in the try push, it seems to only occur at low intermittent frequency (1/5 runs) for the linux1804-64-shippable/opt platform.

Would it be acceptable to mark this test with outcome of ['OK', 'TIMEOUT'] for the specific combination of ubuntu1804 && fission && not debug?

Flags: needinfo?(echen)

I have a try push with the specific condition marked:
https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&tier=1%2C2%2C3&revision=fe278206837fcf3ebf58ed52582d5dfb32c6f515

I will retrigger it at least 15 times to see what the outcomes may be.

Proof of concept push with the test marked with updated expectation of OK, TIMEOUT passes with green for all runs.

https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&tier=1%2C2%2C3&revision=ac0f4c560938fd7f3478e8b01573cc1b3320b930

(In reply to Edwin Takahashi (:egao, :etakahashi) from comment #1)

Would it be acceptable to mark this test with outcome of ['OK', 'TIMEOUT'] for the specific combination of ubuntu1804 && fission && not debug?

Go ahead, but could you help to file a follow-up bug for finding the root cause and remove the test expectation? Thanks.

Flags: needinfo?(echen)

I could keep this bug open for that purpose.

Comment on attachment 9119830 [details]
Bug 1607867 - mark expected outcome of event-before-promise.html for linux1804-64-debug

Revision D59386 was moved to bug 1604714. Setting attachment 9119830 [details] to obsolete.

Attachment #9119830 - Attachment is obsolete: true
Assignee: nobody → egao
Attachment #9119867 - Attachment description: Bug 1607867 - mark expected outcome of promise-rejection-events.html for ubuntu1804 and fission → Bug 1607867 - mark expected outcome of promise-rejection-events.html for ubuntu1804 shippable opt and fission
Pushed by egao@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/aedb120b6e18
mark expected outcome of promise-rejection-events.html for ubuntu1804 shippable opt and fission r=jmaher
See Also: → 1622348
Assignee: egao → nobody
Keywords: leave-open
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: