Closed
Bug 900830
Opened 12 years ago
Closed 12 years ago
dom/plugins/test/unit/test_nice_plugin_name.js fails when using the non-shared plugins directory on Windows
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mihneadb, Unassigned)
References
Details
We introduced a change in the xpcshell test harness that gives every test its own plugins dir to allow running tests concurrently.
This is not really used right now on Windows because of the xpcshell.cpp defaulting to mGREdir/plugins (see bug 899857). I ran the dom/plugins tests on a releng test slave while making sure that they were using the temporary isolated plugins dir, and it turns out that test_nice_plugin_name.js fails.
I suspect it's because of get_test_plugintag (from head_plugins.js), but I don't know all the implementation details.
[I'm referring to the part where the test does:
* copy nptestplugin to npblah
* move nptestplugin away to tmpdir
* check expected perm string ( which yields nptest instead of npblah )
]
It seems that the expected_perm_string looks at the plugin file in the *shared* plugins directory (i.e. mGREdir/plugins) which is untouched, so it has nptest, not npblah.
Comment 1•12 years ago
|
||
Do you have a TBPL link handy for the failures?
Note: I may be slow to respond until monday.
Reporter | ||
Comment 2•12 years ago
|
||
This is from the test slave I played with.
http://pastebin.mozilla.org/2763810
BTW.. -- this is from there as well :)
INFO | Result summary:
INFO | Passed: 1798
INFO | Failed: 3
INFO | Todo: 3
Almost there!
Comment 3•12 years ago
|
||
(In reply to Mihnea Dobrescu-Balaur (:mihneadb) from comment #0)
> We introduced a change in the xpcshell test harness that gives every test
> its own plugins dir to allow running tests concurrently.
[...]
> It seems that the expected_perm_string looks at the plugin file in the
> *shared* plugins directory (i.e. mGREdir/plugins) which is untouched, so it
> has nptest, not npblah.
So, this is still with both $gredir/plugins and $profile/plugins in the plugins dir list?
If so, this should be resolved by bug 899857 and is not really worth looking into on its own.
Flags: needinfo?(georg.fritzsche)
Reporter | ||
Comment 4•12 years ago
|
||
So this should be fixed by bug 899857 but I did encounter the failure again on windows once after that landed. I've marked the tests to run-sequentially for now and we'll try going through them later on after this lands, because this particular bug has been a blocker for quite a while.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•