Hey! The only thing that stands between nf-core/pr...
# pipeline-maintainers
e
Hey! The only thing that stands between nf-core/proteinfamilies and its first release is this AWS failing test: https://cloud.seqera.io/orgs/nf-core/workspaces/AWSmegatests/watch/4YZGs90Hc8Evhq For some reason the CAT_CAT (CAT_HMM) module is not even starting, so I can't get inside a workDir to find out why. The previous job (UNTAR_HMM) seems to execute correctly, producing the right outputs. I've tested with conda/singularity/docker locally and everything runs smoothly. Is there a chance that AWS doesn't like this command?
Copy code
CAT_HMM( UNTAR_HMM.out.untar.map { meta, folder -> [meta, file("$folder/*", checkIfExists: true)] } )
How do people usually test failing stuff on AWS? Thanks..
f
This reminds me of a similar issue we had for #rangeland during AWS testing, here is how we solved it https://nfcore.slack.com/archives/C068T3R7LAE/p1734519704771229?thread_ts=1734425584.443789&cid=C068T3R7LAE you probably want to use
.toUriString()
on that path
❤️ 1
e
OooH! Let me try this!
@Felix Kummer lifesaver!
🚀 1
f
Credit goes to @Adam Talbot for the original fix
⭐ 1
🙌 1
e
Ofc, it's like a pyramid scheme
😆 1
AWS test ran successfully, thanks again!
🚀 4