Closed Bug 1677096 Opened 4 years ago Closed 4 years ago

Intermittent gtest | timed out after 300 seconds without output

Categories

(Testing :: GTest, defect, P5)

Product:
Testing
Component:
GTest
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1115253

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure)

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

What's notable here is that it complains about no output,but there *has been* output. ```
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE

(In reply to Treeherder Bug Filer from comment #0)

What's notable here is that it complains about no output,but there *has been* output. ```

[task 2020-11-13T10:13:06.250Z] 10:13:06     INFO -  TEST-START | ImageDecoders.AVIFStackCheck
[task 2020-11-13T10:18:06.327Z] 10:18:06     INFO -  gtest INFO | gtest | process wait complete, returncode=572
[task 2020-11-13T10:18:06.327Z] 10:18:06  WARNING -  gtest TEST-UNEXPECTED-FAIL | gtest | timed out after 300 seconds without output
[task 2020-11-13T10:18:06.327Z] 10:18:06     INFO -  gtest INFO | rungtests.py exits with code 1

There was no output from the browser for the 5 minutes following 10:13:06.

You need to log in before you can comment on or make changes to this bug.