Intermittent Android 7.0 reftest No tests run or test summary not found
Categories
(Firefox for Android Graveyard :: Testing, defect, P2)
Tracking
(firefox72 fixed)
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
Attachments
(1 file)
It looks like the android reftest harness infrequently fails to complete its logging:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=261812920&repo=mozilla-beta&lineNumber=38196
https://treeherder.mozilla.org/logviewer.html#?job_id=261633920&repo=mozilla-central
https://treeherder.mozilla.org/logviewer.html#?job_id=261212898&repo=autoland
Assignee | ||
Comment 1•5 years ago
|
||
Logcat includes the reftest end-of-suite summary info.
I wonder if this anomaly is related to one of the exceptions seen on shutdown (for both failure and success cases):
08-13 00:39:10.300 2787 2802 I GeckoConsole: 1565653150299 addons.xpi WARN Exception running bootstrap method shutdown on default-theme@mozilla.org: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: resource://gre/modules/Extension.jsm :: shutdown :: line 2339" data: no] Stack trace: shutdown()@resource://gre/modules/Extension.jsm:2339
08-13 00:39:10.300 2787 2802 I GeckoConsole: shutdown()@resource://gre/modules/Extension.jsm:1499
08-13 00:39:10.300 2787 2802 I GeckoConsole: callBootstrapMethod()@resource://gre/modules/addons/XPIProvider.jsm:1789
08-13 00:39:10.300 2787 2802 I GeckoConsole: _shutdown()@resource://gre/modules/addons/XPIProvider.jsm:1918
08-13 00:39:10.300 2787 2802 I GeckoConsole: observe()@resource://gre/modules/AsyncShutdown.jsm:551
08-13 00:39:10.300 2787 2802 I GeckoConsole: onStopped()@resource://reftest/reftest.jsm:790
08-13 00:39:10.300 2787 2802 I GeckoConsole: DoneTests/<()@resource://reftest/reftest.jsm:796
08-13 00:39:10.302 2787 2802 I Gecko : 1565653150299 addons.xpi WARN Exception running bootstrap method shutdown on default-theme@mozilla.org: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: resource://gre/modules/Extension.jsm :: shutdown :: line 2339" data: no] Stack trace: shutdown()@resource://gre/modules/Extension.jsm:2339
08-13 00:39:10.302 2787 2802 I Gecko : shutdown()@resource://gre/modules/Extension.jsm:1499
08-13 00:39:10.302 2787 2802 I Gecko : callBootstrapMethod()@resource://gre/modules/addons/XPIProvider.jsm:1789
08-13 00:39:10.302 2787 2802 I Gecko : _shutdown()@resource://gre/modules/addons/XPIProvider.jsm:1918
08-13 00:39:10.302 2787 2802 I Gecko : observe()@resource://gre/modules/AsyncShutdown.jsm:551
08-13 00:39:10.302 2787 2802 I Gecko : onStopped()@resource://reftest/reftest.jsm:790
08-13 00:39:10.302 2787 2802 I Gecko : DoneTests/<()@resource://reftest/reftest.jsm:796
08-13 00:39:10.303 2787 2802 D GeckoThread: State changed to EXITING
08-13 00:39:10.305 2787 2802 I Gecko : nsWindow[0x765321806800]::Show 0
08-13 00:39:10.306 2787 2802 E GeckoConsole: [JavaScript Error: "TypeError: this.messageManager is null" {file: "resource://gre/modules/GeckoViewContent.jsm" line: 83}]
08-13 00:39:10.306 2787 2802 E GeckoConsole: onDisable@resource://gre/modules/GeckoViewContent.jsm:83:5
08-13 00:39:10.306 2787 2802 E GeckoConsole: set enabled@chrome://geckoview/content/geckoview.js:384:18
08-13 00:39:10.306 2787 2802 E GeckoConsole: init/</<@chrome://geckoview/content/geckoview.js:89:9
08-13 00:39:10.306 2787 2802 E GeckoConsole: forEach@chrome://geckoview/content/geckoview.js:120:19
08-13 00:39:10.306 2787 2802 E GeckoConsole: init/<@chrome://geckoview/content/geckoview.js:88:12
(maybe the log file isn't being flushed because the process is crashing on shutdown??)
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 5•5 years ago
|
||
Low-frequency intermittent failures continue, reported here and in bug 1581345.
Android reftests use the logFile parameter; desktop doesn't. logFile is never explicitly closed -- maybe it should be?
https://treeherder.mozilla.org/#/jobs?repo=try&revision=2f17f52635193037baaeb17a5b67fcdc9ae49eae
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
A speculative fix for intermittent android reftest failures in which the reftest log file
is incomplete but the missing logging is found in the logcat: I hope that closing the
log file explicitly will ensure logging is flushed before the application quits.
Comment 8•5 years ago
|
||
bugherder |
Assignee | ||
Comment 9•5 years ago
|
||
This change didn't resolve the intermittent failures. Failures continue in bug 1581345.
Assignee | ||
Updated•5 years ago
|
Updated•4 years ago
|
Description
•