697737 - Broken Mozmill installation on Linux boxes due to a 'Build' subfolder

Status: RESOLVED FIXED

(Mozilla QA Graveyard :: Infrastructure, defect)

Description

[u279076]

When trying to execute the release_bft.py script today for the 8.0b5#1 builds on Linux and Linux64 VMs on QA-Set I kept seeing the following error:

"cannot connect to jsbridge extension, port 24242"

The scripts stage the tests and start Firefox okay but the tests do not run. Firefox just sits there for a minute then quits with the above error message.

Henrik has just verified the VMs are updated to Mozmill 1.5.6

Comment 1

[Al Billings [:abillings - ex-MoCo]]

In bug 642027 comment 6 (for the new environment), I reported the same problem, which turned out to be an incompatibility with the Nightly mozilla central builds.

Comment 2

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

This is kinda strange. Even after I have updated Mozmill to 1.5.6 on this box, the Add-ons Manager is still reporting Mozmill 1.5.4 being installed.

The reason for the disabled add-ons is the 3rd party fix from Dave which is now part of Firefox Beta.

Anthony, next time please check the Add-ons Manager if the latest version is installed. That would help.

I will now check what's wrong here. I'm kinda looking forward to use our new environments soon. I hate those issues with pip/easy_install upgrades.

Comment 3

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

$ python
Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53) 
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import mozmill
>>> mozmill.version
'1.5.4'

I did the same yesterday after the upgrade to Mozmill 1.5.6 and it has been correctly reported 1.5.6. This is absolutely strange.

Comment 4

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

Looks like this has been caused by the latest upgrade to Ubuntu 11.04, which has been placed Python 2.7 next to Python 2.6 on those boxes. When I uninstall Mozmill for 2.7, the library files still exist in the 2.6 dist-packages folder. A new install just takes those modules instead of downloading the new version.

I think we should simply remove Python 2.6 from those boxes and get rid of the duplicated packages folders.

Comment 5

[Al Billings [:abillings - ex-MoCo]]

I'd like to make new, clean, 11.10 VMs that use the new environment. 11.04 isn't Ubuntu's LTS so there is no reason to keep supporting it. With the new environment, we can start clean on a box. I have to do this for the new ESXi servers soon anyway.

Comment 6

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

Actually this problem has not been caused by an additional Python installation but a 'Build' subfolder under /data/testing. It contained archives of Mozmill 1.5.4 which let pip not download them again. I have seen that reference by running pip with the verbose (-vv) option.

Fixed now by simply removing this subfolder and triggering an upgrade again.

Note: In the future (as long as we don't use the new environments) an upgrade should be not started from within a shell which has a shared folder open.