Open Bug 1629088 Opened 4 years ago Updated 4 years ago

Test times out during try run after only "is" check passed

Categories

(Testing :: Mochitest, defect, P3)

Version 3
defect

Tracking

(Not tracked)

People

(Reporter: mbrodesser-Igalia, Unassigned)

Details

See https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=297153908&repo=try&lineNumber=7244. It contains a link to the corresponding change.

Excerpt from the logs:

[task 2020-04-10T15:16:25.015Z] 15:16:25     INFO - TEST-START | layout/generic/test/test_bug1625057.html
[task 2020-04-10T15:21:52.626Z] 15:21:52     INFO - TEST-INFO | started process screentopng
[task 2020-04-10T15:21:52.782Z] 15:21:52     INFO - TEST-INFO | screentopng: exit 0
[task 2020-04-10T15:21:52.783Z] 15:21:52     INFO - Buffered messages logged at 15:16:25
[task 2020-04-10T15:21:52.783Z] 15:21:52     INFO - TEST-PASS | layout/generic/test/test_bug1625057.html | The clipboard data should correspond to the visually selected
[task 2020-04-10T15:21:52.784Z] 15:21:52     INFO -           text. 
[task 2020-04-10T15:21:52.784Z] 15:21:52     INFO - Buffered messages finished
[task 2020-04-10T15:21:52.784Z] 15:21:52     INFO - TEST-UNEXPECTED-FAIL | layout/generic/test/test_bug1625057.html | Test timed out. 
[task 2020-04-10T15:21:52.784Z] 15:21:52     INFO -     SimpleTest.ok@SimpleTest/SimpleTest.js:299:16
[task 2020-04-10T15:21:52.784Z] 15:21:52     INFO -     reportError@SimpleTest/TestRunner.js:128:22
[task 2020-04-10T15:21:52.784Z] 15:21:52     INFO -     TestRunner._checkForHangs@SimpleTest/TestRunner.js:150:18

Locally, the whole test passed.

The priority flag is not set for this bug.
:ahal, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(ahal)
Flags: needinfo?(ahal)
Priority: -- → P3

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.