Hey there,
I opened a bioconda/bioconda-recipes#22387 whose lint check is failing, but when I click on "View more details on CircleCI Checks" under the checks tab, I get sent to a page with a spinning wheel that never loads and I don't see more details. Can someone help me fix this/tell me how my recipe failed the lint check?
Hi, our monocl3-cli upload failed to quay.io (https://circleci.com/gh/bioconda/bioconda-recipes/110097?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link) due to the following error:
10:49:39 BIOCONDA INFO (ERR) [May 29 10:49:39] ERRO Task processing failed: API error (500): {"message":"Get https://quay.io/v2/dpryan79/mulled_container/manifests/latest: error parsing HTTP 429 response body: invalid character 'T' looking for beginning of value: \"Too many login attempts. \\nPlease reset your Quay password and try again.\”"}should I just retry or is there a password reset as it is advising? Thanks!
https://gist.github.com/bwlang/c33e1cc505ca45c85426ebc1f8f09a3e
let me know if it’s better to write up as an issue in github, i thought maybe this was just my setup...
Yes, I don't know yet what the actual cause is but that's current_repodata.json related. If you do
CONDA_REPODATA_FNS=repodata.json conda create --name=some-env -c conda-forge -c bioconda deeptools=3.4.3you get the latest pysam.
(To make that current_repodata.json omission permanent, you can run
conda config --prepend repodata_fns repodata.json
# if the repodata_fns key is already there (unlikely), also run
conda config --remove repodata_fns current_repodata.json. The conda issue for that is conda/conda#9905 .)
Hey there, can anyone help with an issue with my PR bioconda/bioconda-recipes#22387
It seems that the build system is caching and using an old version of my test script (which is called during build) instead of the one that's up to date in the package distribution on PyPI, but I don't know how this is happening/how to debug it. Or maybe this is an error on my end and I'm not seeing it.
Any help appreciated - I've put more details on the PR.
Bump.
I'm pretty positive my issue is with CircleCI caching the wrong version of trtools. I noticed that CircleCI's checks are pulling trtools-2.0.17 even though the branch now says version = 2.0.18. Any ideas? How can I flush the CircleCI cache and make it run checks on the latest version of my package? bioconda/bioconda-recipes#22387
Here's the PR https://github.com/bioconda/bioconda-recipes/pull/22406/checks?check_run_id=721932723 . Basically, my tests pass the first time on the the configured Docker container, but then the mulled-build fails.
The mulled-build fails because my script doesn't have access to git (it uses git to download files needed for a few of the tests). However, my recipe specifically declares a dependency on git in the test.requires section of meta.yaml. Is this a bug with mulled-build, or an issue with my meta.yaml?
Thanks for any help!
@dpryan79 when you have time, unfortunately the linux upload (which is what I really need) is not working for monocle3-cli and now the error is different:
From ssh://github.com/bioconda/bioconda-recipes
* [new branch] master -> __upstream__xdxlpY8euA/master
Your bioconda-recipes CI configuration is out of date.
Please update it to the latest version of the upstream master branch.
Have @BiocondaBot attempt to fix this by creating a comment on your PR:
@BiocondaBot updateI’m guessing that since that PR is merged now, there is not much point in doing the bot update command, right? Thanks!
requires: section since the point of it is to test that only the package and its run time dependencies are really needed. The normal way we handle this is to put tests with extra requirements in a run_test.sh file. Since that's not installed with the package it's then not run in the mulled test (only those tests still in the meta.yaml are run).
