Closed Bug 1317152 Opened 9 years ago Closed 7 years ago

Intermittent linux debug devtools command timed out: 4800 seconds elapsed running ['/tools/buildbot/bin/python', '-u', 'scripts/scripts/desktop_unittest.py', '--cfg', 'unittests/linux_unittest.py', '--mochitest-suite', 'mochitest-devtools-chrome-chunked'

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: aryx, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell disabled])

Most of these are on aurora and in those cases, the logs are littered with: 19:09:51 INFO - [GFX3-]: Surface width or height <= 0! 19:09:51 INFO - [GFX3-]: Surface width or height <= 0! 19:09:51 INFO - [GFX3-]: Surface width or height <= 0! https://dxr.mozilla.org/mozilla-central/rev/34fce7c12173bdd6dda54c2ebf6d344252f1ac48/gfx/2d/Factory.cpp#257 :ryanvm -- do you know what that's about, by chance?
Flags: needinfo?(ryanvm)
I don't, sorry. I do know that in general, these tests are timing out like mad lately and someone needs to track it down. I started a thread on sheriffs@ about it, but it doesn't seem to be making much progress. I also sorta-suspect that this is related to bug 1316632 as they have very similar regression ranges and many of the screenshots in the log show spinners. But I don't have cycles to look into it further than that, though. Sorry.
Flags: needinfo?(ryanvm)
Thanks Ryan. I have noticed several aurora-only or aurora-mostly timeout bugs seem closely associated with those log messages. I'll try to find a regression range.
Depends on: 1323625
Depends on: 1328915
Whiteboard: [stockwell disabled]
There was a temporary infra problem affecting os-x today, bug 1363893. Many of these failures seemed more correlated with bug 1362822, backed out twice today.
Component: General Automation → General
I think this bug outlived its usefulness. Closing this, feel free to reopen if I'm wrong.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.