Closed
Bug 563638
Opened 15 years ago
Closed 15 years ago
EXCEPTION: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch2.getBoolPref]" when trying to run reftests on fennec using recent tests package
Categories
(Testing :: Reftest, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: martijn.martijn, Unassigned)
Details
I was trying to run reftests on fennec on windows and I used this tests package for that:
http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-1.9.2-win32-unittest/1272916419/firefox-3.6.5pre.en-US.win32.tests.zip
But there seems to be a problem with that, because I got this error, when trying to run the reftests with that:
mw22@MW22-PC /c/tests
$ python reftest/runreftest.py --xre-path=../Users/mw22/Desktop/moz/fennec_bui
lds/fennec192_20100503/xulrunner --appname=../Users/mw22/Desktop/moz/fennec_bui
lds/fennec192_20100503/fennec.exe reftest/tests/layout/reftests/reftest.list
REFTEST INFO | runreftest.py | Performing extension manager registration: start.
INFO | automation.py | Application pid: 7380
INFO | automation.py | Application ran for: 0:00:02.351000
INFO | automation.py | Reading PID log: c:\users\mw22\appdata\local\temp\tmpmnsf
pspidlog
REFTEST INFO | runreftest.py | Performing extension manager registration: end.
REFTEST INFO | runreftest.py | Running tests: start.
INFO | automation.py | Application pid: 6548
REFTEST TEST-UNEXPECTED-FAIL | | EXCEPTION: [Exception... "Component returned fa
ilure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch2.getBoolPref]" nsre
sult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://reftes
t/content/reftest.js :: anonymous :: line 307" data: no]
REFTEST FINISHED: Slowest test took 0ms (undefined)
REFTEST INFO | Result summary:
REFTEST INFO | Successful: 0 (0 pass, 0 load only)
REFTEST INFO | Unexpected: 1 (0 unexpected fail, 0 unexpected pass, 0 unexpected
asserts, 0 unexpected fixed asserts, 0 failed load, 1 exception)
REFTEST INFO | Known problems: 0 (0 known fail, 0 known asserts, 0 random, 0 ski
pped)
REFTEST INFO | Total canvas count = 0
REFTEST INFO | Quitting...
INFO | automation.py | Application ran for: 0:00:01.987000
INFO | automation.py | Reading PID log: c:\users\mw22\appdata\local\temp\tmpxuur
3spidlog
WARNING | automationutils.processLeakLog() | refcount logging is off, so leaks c
an't be detected!
REFTEST INFO | runreftest.py | Running tests: end.
The javascript error in the reftest.js file points to bug 555289. Ehsan, do you have an idea what's going on here?
Reporter | ||
Comment 1•15 years ago
|
||
Ok, when I remove the contents of the C:\tests\reftest\tests\modules\plugin\test\reftest\reftest.list file, then I get things to work.
It turns out that the reftest.js file in reftest.jar in the windows tests package don't seem to have the getBoolPref additions that the patch in bug 555289 added.
No idea why.
Comment 2•15 years ago
|
||
How are those packages built? Can you diff the reftest.js file inside reftest.jar with the one living in the tree?
Reporter | ||
Comment 3•15 years ago
|
||
Sorry, I don't know how those packages are built. I guess those packages need to be updated. Probably not something you need to do.
Maybe it will happen automatically at some point?
Comment 4•15 years ago
|
||
Maybe someone @ releng knows? Chris, could you please CC someone who can help us here, if you don't know the answer yourself?
Comment 5•15 years ago
|
||
Is it valid to use Firefox desktop reftests against Fennec? (Since the linked test zip is Firefox desktop).
Comment 6•15 years ago
|
||
Re comment 5: we should (hopefully) start uploading packaged tests for win32 fennec starting tonight, so you shouldn't have to use Firefox desktop tests. (bug 564272)
Reporter | ||
Comment 7•15 years ago
|
||
Thanks, Aki. Feel free to close this bug, if you think it's appropriate.
Comment 8•15 years ago
|
||
Sure, open a new one if you see issues with the new test zips.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•