958680 - mozmill doesn't work with extensions that contain symlinks

Status: RESOLVED WONTFIX

(Testing :: Mozbase, defect)

Description

[serge]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.62 Safari/537.36

Steps to reproduce:

Copy the directory (we'll call the original DIR_ORIG and the new one DIR) of an existing bootstrapped extension.
DIR should contain bootstrap.js and install.rdf, among others.
Remove bootstrap.js from DIR
Add a softlink from DIR_ORIG's bootstrap.js (ln -s DIR_ORIG/bootstrap.js DIR/boostrap.js)
Run mozmill with any test and with -a DIR


Actual results:

The browser does not load the extension. This can be verified by placing a log statement in the bootstrap.js file. If however, the original (non-symlinked) extension is used, the extension is correctly loaded into the browser.


Expected results:

The browser should have loaded the extension with the symlinked bootstrap.js.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

What Mozmill does is to create a copy of DIR by placing its content into the extensions/staged folder of the newly created profile. Usually this should work if the specified dir is a symlink. Actually I never tested it, if a single file in DIR is a symlink. Serge, can you please test the whole dir symlink situation? Does that work for you?

If you only symlink the bootstrap.js file, is this file being copied into the profile or not? Would assume not.

We explicitly allow copying of symlinks here, so I'm not sure what's going wrong in your case:
https://github.com/mozilla/mozbase/blob/master/mozprofile/mozprofile/addons.py#L373

Comment 2

[Geoff Brown [:gbrown]]

Mass closing bugs with no activity in 2+ years. If this bug is important to you, please re-open.