Skip to content

This fixes a bug where we weren't locking the Python env. #2286

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 7, 2016

Conversation

ericholscher
Copy link
Member

@ericholscher ericholscher commented Jul 6, 2016

This lead to the Text File Busy errors,
because we were trying to create the virtualenv while another process was running.
Instead of this throwing a "version locked" error and retrying,
it was just failing because it was never checking for a lock properly.

Fixes #2229

This lead to the `Text File Busy` errors,
because we were trying to create the virtualenv while another process was running.
Instead of this throwing a "version locked" error and retrying,
it was just failing because it was never checking for a lock properly.
@ericholscher
Copy link
Member Author

Not sure this is the best approach -- this would give us 3 seperate locking steps on a build (VCS checkout, env setup, and doc building) -- we should probably just use a single lock. The main issue here is that we want to run the VCS checkout updates in a task from webhook endpoints, so it also needs the locking logic. Should be pretty simple to just put a lock=False argument when running it from inside the tasks though.

@agjohnson
Copy link
Contributor

I think that makes sense. If you have any specific thoughts on a locking refactor, open up an issue to track that.

+1 on this for now though.

@agjohnson agjohnson merged commit b84ebeb into master Jul 7, 2016
@agjohnson agjohnson deleted the lock-python-env-setup branch July 7, 2016 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants