Testing for the fork server without the install directory
Categories
(Core :: IPC, enhancement)
Tracking
()
People
(Reporter: jld, Unassigned)
References
(Blocks 1 open bug)
Details
If we use the fork server, we need to deal with the case where the install directory is updated (or removed) underneath the running install. Right now, we won't crash immediately (because we'll have an executable and libxul that matches the parent process) but it will still have the wrong omnijars, etc.
I've been testing this manually by running chmod 0 after the browser is started (and turning off content process prelaunch) and then trying various things, but we should have a way of doing this in automated testing. (I used chmod 0 because moving the install directory doesn't entirely work — I observed some failures but there was at least one thing that found the new location, probably via /proc/self/exe.)
I've been told that Marionette is the right framework for tests that need to restart the browser like this, but I've also been told that Marionette is deprecated, and it may also be useful to be able to run existing tests in this setup, so maybe this should be hacked into one or more of the existing test runners. This requires more investigation.
Description
•