Hi everyone, I get this error when testing a tool called netmhcpan: https://github.com/nf-core/epitopeprediction/actions/runs/20831414558/job/59846268068?pr=318#step:8:229 The reason is: the tool cannot handle file paths exceeding a length of ~160 chars or so. nf-test (I guess under the hood nextflow) generates these nested long directory names. I checked locally when specifying e.g.

bash -l -c "export NFT_WORKDIR=/tmp/nft && nf-test test tests/netmhcpan.nf.test --profile=+docker --update-snapshot"

it runs through. with default .nf-test workdir I get the same error as in CI. Anything I can do about it on CI to fix it?

In the nf-test GitHub CI action,

NFT_WORKDIR

is set to

~

by default. Have you already tried changing that? https://github.com/nf-core/epitopeprediction/blob/4c13c15b46ec69e959faf2cf338e9ceb795a19d5/.github/workflows/nf-test.yml#L22

Thanks for quick response. I am going to try

/tmp

Nice solve @Usman, we noticed a similar issue in #C0110R22NH3 first, and I used @Sarai's fix in other projects, I'm thinking of trying to push it back to TEMPLATE

Why do tools set a limit on the file path length? 😅

Older tools do sometimes 👀