Closed Bug 974930 Opened 12 years ago Closed 8 years ago

Test failure "Add-on has been specified. - got 'undefined'" in restartTests

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Type:
defect

Tracking

(firefox29 affected, firefox30 affected, firefox31 affected, firefox32 affected, firefox33 affected, firefox34 affected)

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox29 --- affected
firefox30 --- affected
firefox31 --- affected
firefox32 --- affected
firefox33 --- affected
firefox34 --- affected

People

(Reporter: cosmin-malutan, Unassigned)

References

(
URL
)

Details

(Whiteboard: [mozmill-test-failure])

This failed with Aurora/Holy-Branch en-US on Mac 10.6 mm-osx-106-3 http://mozmill-daily.blargon7.com/#/functional/report/6062fdddb60e88657bc78ec1f46e7842
Failed today with Aurora/Holy-Branch en-US - Mac OS X 10.6 [testrun - project_functional] http://mozmill-daily.blargon7.com/#/functional/report/e248c845ffb052c61b3635551b702549
Making this a more general bug giving that we see this in several tests and that's related to a library method. Failed today with testAddons_installFromFTP/test2.js, with os x 10.6.8, default en-US: http://mozmill-daily.blargon7.com/#/remote/report/3ed2024184b13bf096824c08080352c2 Also with testAddons_enableDisableExtension/, same 10.6.8, default de: http://mozmill-daily.blargon7.com/#/functional/report/3ed2024184b13bf096824c0808181dad And with testAddons_installUninstallSoftBlocklistedExtension/, osx 10.7.5, default de: http://mozmill-daily.blargon7.com/#/functional/report/3ed2024184b13bf096824c0808184688
status-firefox30: --- → affected
Priority: -- → P2
Summary: Test failure "Add-on has been specified. - got 'undefined'" in testAddons_uninstallExtension/test3.js → Test failure "Add-on has been specified. - got 'undefined'" in restartTests
Failed again on Nightly en-US with Windows 8 (x86): http://mozmill-daily.blargon7.com/#/remote/report/eeab4d15c588c5e6f00ab97aa53d625b
status-firefox31: --- → affected
OS: Mac OS X → All
Hardware: x86_64 → All
Failed yesterday with Aurora de on OS X 10.8.5, testAddons_installFromFTP/test2.js: http://mozmill-daily.blargon7.com/#/remote/report/91f18c799f60f33fc05d03749c4257ef
status-firefox32: --- → affected
Whiteboard: [mozmill-test-failure]
I've marked several tests as duplicate to this one. There seems to be a general problem to installing / loading addons in several places (there's a chance its the same issue). We've had another one for example: http://mozmill-daily.blargon7.com/#/functional/report/2f56cb3a3728c2c47cd1b44f771fdd25
(In reply to Andreea Matei [:AndreeaMatei] from comment #11) > Happened again over several tests: > http://mozmill-release.blargon7.com/#/functional/report/ > ee6ae3df35a164c4abc5cec1a3a4fb79 > http://mozmill-release.blargon7.com/#/functional/report/ > ee6ae3df35a164c4abc5cec1a3a7ae52 > http://mozmill-release.blargon7.com/#/functional/report/ > ee6ae3df35a164c4abc5cec1a3a3ed17 > http://mozmill-daily.blargon7.com/#/functional/report/ > ee6ae3df35a164c4abc5cec1a3afc12e All these instances are actually bug 972912. In all cases test2 was not run, so the addon indeed was not installed.
This time is real :) on OSX 10.7, beta it: Test1.js has ran for both testAddons_enableDisableExtension and testAddons_installUninstallSoftBlocklistedExtension: http://mozmill-release.blargon7.com/#/functional/report/2f982f72826307fed840a3b11c4b99ca
Ah nice, some relevant info: > 03:44:02 TEST-START | restartTests/testAddons_installFromFTP/test1.js | setupModule > 03:44:02 TEST-START | restartTests/testAddons_installFromFTP/test1.js | testInstallAddonFromFTP > 03:44:04 TEST-PASS | restartTests/testAddons_installFromFTP/test1.js | testInstallAddonFromFTP > 03:44:04 TEST-START | restartTests/testAddons_installFromFTP/test1.js | teardownModule > 03:44:04 TEST-END | restartTests/testAddons_installFromFTP/test1.js | finished in 1965ms > 03:44:05 1411468021886 addons.xpi WARN Failed to install /Users/mozauto/Library/Caches/TemporaryItems/tmp-10o.xpi from ftp://ftp.mozqa.com/data/firefox/addons/extensions/empty.xpi: [Exception... "AddonManager is not initialized" nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: resource://gre/modules/AddonManager.jsm :: AMI_callInstallListeners :: line 1399" data: no] Stack trace: AMI_callInstallListeners()@resource://gre/modules/AddonManager.jsm:1399 < AMP_callInstallListeners()@resource://gre/modules/AddonManager.jsm:2372 < AI_startInstall/<()@resource://gre/modules/addons/XPIProvider.jsm:5591 < TaskImpl_run()@resource://gre/modules/Task.jsm:330 < Handler.prototype.process()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:865 < this.PromiseWalker.walkerLoop()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744 < Spinner.prototype.observe()@resource://gre/modules/AsyncShutdown.jsm:347 < <file:unknown> > 03:44:05 ************************* > 03:44:05 A coding exception was thrown in a Promise rejection callback. > 03:44:05 See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise > 03:44:05 Full message: TypeError: this.installs is null > 03:44:05 Full stack: XPI_removeActiveInstall@resource://gre/modules/addons/XPIProvider.jsm:3656:9 > 03:44:05 AI_startInstall/<@resource://gre/modules/addons/XPIProvider.jsm:5697:7 > 03:44:05 Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:868:21 > 03:44:05 this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:7 > 03:44:05 Spinner.prototype.observe@resource://gre/modules/AsyncShutdown.jsm:347:9 > 03:44:05 > 03:44:05 ************************* > 03:44:09 TEST-START | restartTests/testAddons_installFromFTP/test2.js | setupModule > 03:44:09 TEST-START | restartTests/testAddons_installFromFTP/test2.js | testAddonInstalled > 03:44:10 ERROR | Test Failure | { > 03:44:10 "exception": { > 03:44:10 "message": "AddonsManager_isAddonInstalled: Add-on has been specified. - got 'undefined'", > 03:44:10 "lineNumber": 376, > 03:44:10 "name": "Error", > 03:44:10 "fileName": "file:///Users/mozauto/jenkins/workspace/mozilla-aurora_remote/data/mozmill-tests/lib/addons.js" > 03:44:10 } > 03:44:10 } > 03:44:10 TEST-UNEXPECTED-FAIL | restartTests/testAddons_installFromFTP/test2.js | testAddonInstalled > 03:44:10 TEST-START | restartTests/testAddons_installFromFTP/test2.js | teardownModule > 03:44:10 TEST-END | restartTests/testAddons_installFromFTP/test2.js | finished in 907ms We actually failed to install the addon apparently.
Clearly an Add-ons Manager related bug, which you should file.
Same failure in a differen place: http://mozmill-release.blargon7.com/#/functional/report/bfd52839a01858de2f33d25f7674f61d Will file a bug shortly
Depends on: 1072768
New failure: http://mozmill-release.blargon7.com/#/functional/report/4b004f9a9a3a5bc3aa0f3a07c1441af1 As said in bug 1072768 comment 3 we should enable `extensions.logging.enabled` on some (all?) addon tests, so when this fails again we have some more info.
Another failure on Fx 35.0 RC build3 th locale on OS X 10.6.8: http://mozmill-release.blargon7.com/#/remote/report/b286a409cd8303a08379842fe436da7f
Mozmill tests have been superseded by Marionette tests.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.