Closed Bug 1406806 Opened 8 years ago Closed 8 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT | browser/extensions/screenshots/test/browser/browser_screenshots_ui_check.js | application timed out after 330 seconds with no output

Categories

(Firefox :: Screenshots, defect, P5)

Product:
Firefox
Component:
Screenshots
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Assigned: jhirsch)

Details

(Keywords: intermittent-failure)

Component: WebExtensions: Untriaged → Screenshots
Product: Toolkit → Firefox
Assignee: nobody → jhirsch
Hmm. This line in live_backing.log seems odd: 12:54:36 INFO - GECKO(779) | Extension error: TypeError: photonPageAction is null resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///Users/cltbld/tasks/task_1507477146/build/application/NightlyDebug.app/Contents/Resources/browser/features/screenshots@mozilla.org.xpi!/bootstrap.js 271 At line 271, where the error occurs, I don't think we should have a photonPageActionPort and a null photonPageAction. :adw, do you think I should investigate this further, or could this be a one-time failure that's safe to ignore?
Flags: needinfo?(adw)
Nice catch, Jared. Hmm, that would seem to imply that the webextension side is still sending over a message even after stop() has been called. Maybe that's possible? It would be easy to bail from the port listener if photonPageAction is null to avoid the exception. But that seems like it might be separate from the timeout... Messages to the port are sent asyncly, I would imagine? I wouldn't expect an exception in a listener to cause the whole browser to hang or crash. And the log has this: > 12:54:45 INFO - Browser Chrome Test Summary > 12:54:45 INFO - Passed: 1 > 12:54:45 INFO - Failed: 0 > 12:54:45 INFO - Todo: 0 > 12:54:45 INFO - Mode: e10s > 12:54:45 INFO - *** End BrowserChrome Test Results *** So the test actually finished? That's right before this: > 12:54:46 INFO - GECKO(779) | Assertion failure: 0 == rv, at /builds/worker/workspace/build/src/nsprpub/pr/src/pthreads/ptthread.c:870 So I'd say let's ignore this for now. If it happens again, we might get more data to better understand what's going on. Or if we don't but it keeps happening, then let's take a closer look. But it kind of looks like a one-off to me right now.
Flags: needinfo?(adw)
https://wiki.mozilla.org/Bugmasters#Intermittent_Test_Failure_Cleanup
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.