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

Bumped cnvkit version #5926

Closed
wants to merge 2 commits into from
Closed

Bumped cnvkit version #5926

wants to merge 2 commits into from

Conversation

micknudsen
Copy link
Member

  • 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).

@micknudsen
Copy link
Member Author

How does one proceed when Travis runs out of time?

@bgruening
Copy link
Member

I guess this was just a hiccup with travis as the OSX build was successful. I restarted the build.

@micknudsen
Copy link
Member Author

Thanks. Unfortunately it timed out again. Same thing happened in my own fork. Restarted a couple of times, but same thing...

@etal
Copy link
Contributor

etal commented Sep 6, 2017

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?

@bgruening
Copy link
Member

Ok, lets see what happens with increased logging :)

@etal
Copy link
Contributor

etal commented Sep 7, 2017

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?

@bgruening
Copy link
Member

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.

@micknudsen
Copy link
Member Author

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?

@daler
Copy link
Member

daler commented Sep 25, 2017

I wonder if we're hitting a known bug in conda caused by too many duplicated R pacages across conda-forge, bioconda, and r channels. The issue in conda/conda#5536 suggests modifying your ~/.condarc to remove the r channel from defaults (as in this particular comment: conda/conda#5536 (comment)).

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.

@chapmanb
Copy link
Member

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.

@chapmanb chapmanb closed this Oct 13, 2017
@micknudsen micknudsen deleted the bump_cnvkit branch October 13, 2017 10:42
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.

None yet

5 participants