https://nf-co.re logo
Join Slack
Powered by
Hi everyone! I could use some help debugging a CI ...
# help
o
Hi everyone! I could use some help debugging a CI issue. Here it is github.com/nf-core/…/84719847978 (conda | 25.04.0 | 2/7). The Conda tests are failing because the pipeline cannot detect the 
carveme
version. In the snapshot, I get:
Copy code
Expected:
"carveme": "1.6.6"

Found:
"carveme": null
Docker and Singularity tests pass without any issues. The problem only occurs in the Conda CI environment, where it seems that 
pip show carveme
(or the version detection) returns nothing. So far I've tried: updating 
.github/actions/nf-test/action.yml
to use the latest template (
setup-miniconda
v4 instead of v3), returning to the default template without Clean Conda cache setting (which led me to the error 
no space left on device
) I also talked with @Evangelos Karatzas, maintainer of carveme, and confirmed that the CI tests in the module are passing correctly. Has anyone seen 
pip show
(or version detection) fail only in the GitHub Actions Conda environment?cc @mashehu, in case you've seen something similar.
quick look 1
e
I am refreshing the singularity container to make sure the version printing works locally
Copy code
Singularity> pip show carveme | sed -n 's/^Version: //p'
WARNING: The directory '/home/vangelis/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
1.6.6
I wonder if this Warning plays a roll in the null error
and now trying with conda (sorry just waking up xD)
for conda there is no warning at all:
Copy code
pip show carveme | sed -n 's/^Version: //p'
1.6.6
m
can you try 
which pip
@Evangelos Karatzas?
e
pip 26.1.2 for my conda and 25.3 for singularity
m
nope, not the version. just want to know if there is a pip in your env.
e
yep: /tmp/carveme-carve-env-codex/lib/python3.14/site-packages/pip
m
i have a feeling pip is not present in the CI run on the pipeline (compared to modules repo). looking into the differences in setup there.
yep, rerunning the tests in the CI also puts out an empty string now (but I added an alternative way that seems to work) https://github.com/nf-core/modules/actions/runs/28649146296/job/84962891814?pr=12232
👍 1
o
Thank you!!
m
7 Views
Open in Slack
PreviousNext
Powered by