Skip to content
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

[17.05] Try activating conda environment again if previous activation failed #4035

Merged

Conversation

mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented May 5, 2017

That should resolve #4031.

@bgruening
Copy link
Member

Good idea @mvdbeek! 👍

while [ $COUNT -lt $MAX_TRIES ]; do
. %s '%s' > conda_activate.log 2>&1
if [ $? -eq 0 ];then
break
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indentation.

sleep 10s
let COUNT=COUNT+1
fi
done """
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this may not have exit code 1 if the activation fails all 3 times.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's right, it will just continue and fail with command not found, which is OK, no ?

@nsoranzo nsoranzo requested a review from natefoo May 5, 2017 22:30
@jmchilton
Copy link
Member

Thanks @mvdbeek - this seems like a good idea. I have mixed feelings on the explicit exit - it isn't something we have done in the past but it is probably better to be explicit here.

@jmchilton jmchilton merged commit 9e6c152 into galaxyproject:release_17.05 May 8, 2017
@galaxybot
Copy link
Contributor

This PR was merged without a milestone attached.

@jmchilton jmchilton added this to the 17.05 milestone May 8, 2017
@mvdbeek mvdbeek deleted the retry_conda_activation branch June 12, 2018 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants