-
Notifications
You must be signed in to change notification settings - Fork 355
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
Make installation and upgrading more robust #3191
Comments
hackdna
changed the title
Update bcbio_nextgen_install.py to Python 3
Make installation more robust
Apr 15, 2020
hackdna
changed the title
Make installation more robust
Make installation and upgrading more robust
Apr 15, 2020
@amizeranschi thanks for heads up. Looks like @naumenko-sa is helping you figure it out. |
Yes, the issue is now solved. Many thanks to you guys for working on bcbio-nextgen! |
This was referenced May 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issues often arise due to runtime errors during installation or upgrading of bcbio, for example: #3165, #3169, #3180, #3265, #3318, etc. Other issues arise due to coding errors, for example: #3168, #3188, etc.
In many cases error messages don't provide enough information to the users, for example: "subprocess.CalledProcessError: Command returned non-zero exit status 1".
Issues due to runtime errors can be reduced by better error handling that provides more informative error messages. Issues due to coding errors can be reduced by running the installer as part of Travis CI builds or at least adding that as an additional step of the release process.
The text was updated successfully, but these errors were encountered: