Closed Bug 983161 Opened 10 years ago Closed 10 years ago

Test failure 'AddonsManager_getAddonChildElement: Add-on has been specified. - got 'undefined'' in /restartTests/testAddons_uninstallExtension/test4.js

Categories

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

x86_64
macOS
defect

Tracking

(firefox30 affected, firefox31 affected)

RESOLVED DUPLICATE of bug 974930
Tracking Status
firefox30 --- affected
firefox31 --- affected

People

(Reporter: andrei, Unassigned)

References

()

Details

(Whiteboard: [mozmill-test-failure])

Module:    testUninstallEnabledExtension
Test:      /restartTests/testAddons_uninstallExtension/test4.js    
Failure:   AddonsManager_getAddonChildElement: Add-on has been specified. - got 'undefined'
Branches:  default
Platforms: OSX 10.6

Report: http://mozmill-daily.blargon7.com/#/functional/report/d8c9b09561f242bc8489be43d6331055

1 occurrence thus far.

The failure came while calling `removeAddon` here:
http://hg.mozilla.org/qa/mozmill-tests/file/63ba09ddd84a/firefox/tests/functional/restartTests/testAddons_uninstallExtension/test4.js#l50

Which might mean that the previous call to `getAddons` didn't return the addon.
Failed with Aurora en-US (20140322004001) on Mac OSX 10.6 (mm-osx-106-3)
http://mozmill-daily.blargon7.com/#/functional/report/2686ef5c08d17b800fd2f557bf05c945
OS: All → Mac OS X
Hardware: All → x86_64
Again with Aurora it (20140324150430) on Mac osx 10.6 (mm-osx-106-3)
http://mozmill-daily.blargon7.com/#/functional/report/97976110c92e838016d17f7fb247d031
I ran into a failure here http://mozmill-release.blargon7.com/#/functional/report/3ed251269efbb25c65b0fc5d9d37bfdd   while running the functional reports for the 31 merge to beta 1. test3 and test4 both failed. 

test3: testUninstallDisabledExtension; AddonsManager_isAddonEnabled: Add-on has been specified. - got 'undefined' 
test4: testUninstallEnabledExtension; aSpec.addon is undefined 

Does test3 need its own bug or should I just report it here?
If test3 fails, test4 will certainly fail too. I think what you are looking for is bug 974930.
(In reply to Henrik Skupin (:whimboo) from comment #6)
> If test3 fails, test4 will certainly fail too. I think what you are looking
> for is bug 974930.

That's different. The one mentioned by Liz is fallout from bug 972912. Specifically test2 is missing from the report.
This is happening frequently on Beta -- if it's not going to get fixed in time, can we please disable this test?
Depends on: 1036294
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.