Closed Bug 898716 Opened 12 years ago Closed 12 years ago

land virtualenv changes from beagle branch

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Assigned: mozilla)

References

Details

(Whiteboard: [mozharness])

Attachments

(1 file)

the python.py changes here: https://github.com/escapewindow/mozharness/compare/master...beagle This should make the beagle review go smoother.
Attached patch virtualenvSplinter Review
This patch does two things: * gets rid of the useless _check_existing_virtualenv() method. I put this in place because I was having issues if I ran virtualenv calls while I had another virtualenv activated, but I think that was operator error. I haven't seen those issues in recent memory. * allows for virtualenv updates in create_virtualenv(). Basically, the existing create_virtualenv() will halt the script if the virtualenv already exists, which forces us to clobber the virtualenv and recreate it on every pass. I found this to be the wrong behavior in my hg-git work, since the modules should change rarely, but I don't want to have to clobber everything to be able to update the module list in an automated way.
Attachment #786058 - Flags: review?(rail)
Attachment #786058 - Flags: review?(rail) → review+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: