Closed Bug 1210669 Opened 9 years ago Closed 8 years ago

Intermittent gtest TEST-UNEXPECTED-FAIL | gtest | test failed with return code 1 from Moz2D.JobScheduler_Join

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox44 --- affected

People

(Reporter: philor, Assigned: nical)

References

Details

(Keywords: intermittent-failure) 

You'll probably find the previous instances of this starred as bug 1115253.

https://treeherder.mozilla.org/logviewer.html#?job_id=15074225&repo=mozilla-inbound

17:23:13     INFO - TEST-START | Moz2D.JobScheduler_Join
17:23:15  WARNING - gtest TEST-UNEXPECTED-FAIL | gtest | test failed with return code 1
Assignee: nobody → nical.bugzilla
Looking at all of the entries in https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1210669&startday=2015-10-26&endday=2015-11-01&tree=all and most of them are not related to the JobScheduler tests. A good half of the failures are in the ImageDecodeToSurface gtest. I am interested in the JobScheduler ones, though. There are a few, but none of them have any information about the nature of the failure (no stack trace, no warning or error message associated to an assert, ect.), Just:

> 20:36:06  WARNING - gtest TEST-UNEXPECTED-FAIL | gtest | test failed with return code 1

Does that mean that the test is killed by the harness because of a timeout threshold? the scheduler tests can easily take a few seconds each, so if the test suite is close to the timeout limit it would not be surprising that we hit the limit in the scheduler tests more often than the others, but if it's a deadlock (which is what the test is trying to bust out), it's kind of a big deal. However, all of the failures I have looked at so far happen after the test has run for only about 2 seconds so it doesn't seem like a deadlock.
Flags: needinfo?(philringnalda)
Doesn't look anything like a timeout to me. I would expect timeouts to look like those rare instances starred against bug 1115253 which are actually that bug, though most of them and all of the current ones are actually either this bug or bug 1191347.
Flags: needinfo?(philringnalda)
Blocks: 1239292
I think that this got fixed by the patch in bug 1239288.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.