-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Bumped cnvkit version #5926
Bumped cnvkit version #5926
Conversation
micknudsen
commented
Sep 1, 2017
- I have read the guidelines for bioconda recipes.
- This PR adds a new recipe.
- AFAIK, this recipe is directly relevant to the biological sciences (otherwise, please submit to the more general purpose conda-forge channel).
- This PR updates an existing recipe.
- This PR does something else (explain below).
How does one proceed when Travis runs out of time? |
I guess this was just a hiccup with travis as the OSX build was successful. I restarted the build. |
Thanks. Unfortunately it timed out again. Same thing happened in my own fork. Restarted a couple of times, but same thing... |
Looks like this build completes in 15 minutes on OS X, and bails after 1.5 hours on Linux. Is there anything I can change upstream (or via dependency versions) to speed this up? |
Ok, lets see what happens with increased logging :) |
If I'm reading the logs right, mulled-build takes a bit over an hour for each Python version, and the timeout lands in the middle of the second execution. (1) Is that expected? (2) Would it be possible to split the dockerization for Python 2.7 and Python 3.5 into separate jobs to stay under the 90-minute limit? |
No this is not expected, a build is more or less a copy of the PREFIX into a container and then running the tests in this new container. I have no clue why this takes so long. I will try to reproduce it locally. |
I have recently had troubles installing certain bioconda packages. Solving dependencies ran for more than a day, so I killed the jobs (-vvv, the extremely verbose option, indicated progress, so it didn't just stall). This also happened for cnvkit, but today it all of sudden just worked. Maybe this was to blame? Could you please try to restart the build? |
I wonder if we're hitting a known bug in conda caused by too many duplicated R pacages across I think it will be worth it to convert bioconda-utils to using such a modified condarc. I'll add an issue in bioconda-utils. |
Thanks so much for all this work. I've been trying to debug this and couldn't replicate it with the latest packages so tried and submission and all passed smoothly. I wonder if this was related to the move to 3.4.1 on going at the time? Either way, I ended up bumping CNVkit to 0.9.0 so we should have the latest version now. Thanks again for all the work on this and hopefully all goes smooth on future updates. |