Niklas Schandry
02/11/2025, 1:13 PMNiklas Schandry
02/11/2025, 1:14 PMtrue has been detected.` but the pipeline is called as
nextflow run ./genomeassembler/$( sed 's/\W/_/g' <<< dev) -stub -profile test,singularity --outdir ./results and i dont see any true or positional argument, I also do not really know what the sed part is doing tbhNiklas Schandry
02/11/2025, 1:16 PMmashehu
02/11/2025, 1:25 PM-stub doesn’t have any value and is therefore triggering tthis warning . can be ignored.
can you download the pipeline locally and run it with the command in the CI locally?Niklas Schandry
02/11/2025, 1:25 PMmashehu
02/11/2025, 1:26 PMNiklas Schandry
02/11/2025, 1:26 PMNiklas Schandry
02/11/2025, 1:29 PMdoes your pipelilne support stub runs?maybe I have not tested stub runs, I have added stubs for the modules that did not have one and are part of the test, this did not help. But it should run afterwards in a non-stub, correct? That step also fails without any error message
Niklas Schandry
02/11/2025, 1:29 PMERROR ~ Pipeline failed. Please refer to troubleshooting docs: https://nf-co.re/docs/usage/troubleshootingmashehu
02/11/2025, 1:33 PMCannot invoke method clone() on null object means one of the modules doesn’t have a stub mode (yet), see discussion here https://nfcore.slack.com/archives/C07BDPBPLG3/p1734347460850619Niklas Schandry
02/11/2025, 1:33 PMNiklas Schandry
02/11/2025, 1:34 PMmashehu
02/11/2025, 1:35 PMmashehu
02/11/2025, 1:36 PMmashehu
02/11/2025, 1:36 PMNiklas Schandry
02/11/2025, 1:36 PMNiklas Schandry
02/11/2025, 1:36 PMmashehu
02/11/2025, 2:12 PMNiklas Schandry
02/11/2025, 2:20 PMNiklas Schandry
02/11/2025, 2:40 PMdev and not the branch that is in the PR? I.e. I would only see if I fixed it after merging? I have enabled GHA to trigger on PRs (to see if it works before merging) but it is not unlikely that I forgot to change something and it is still running dev..mashehu
02/11/2025, 2:43 PMNiklas Schandry
02/11/2025, 2:46 PMNiklas Schandry
02/11/2025, 2:46 PMNiklas Schandry
02/11/2025, 2:52 PMNiklas Schandry
02/11/2025, 2:53 PMNiklas Schandry
02/11/2025, 3:18 PMmashehu
02/11/2025, 3:26 PMMatthias Zepper
02/11/2025, 4:38 PMI also do not really know what the sed part is doing tbhGenerating the correct path to the download directory. If you are downloading the
dev revision of genome assembler, the pipeline code will be in genomeassembler/dev/. But if you are downloading the revision v2.10, it will be genomeassembler/v2_10/
Because you can download arbitrary branches, I can’t hardcode the full output path in the action.
But when it tries running $( sed 's/\W/_/g' <<< dev), you are indeed downloading and testing dev and not your featurebranch. In your more recent runs, it is then gha_download.
Runs in your own fork should be available, since it is an open-source repo. You can launch them e.g. like so:
gh workflow run -R "nschan/genomeassembler" --ref "fix_ci_download" --field "testbranch=nschan:fix_ci_download" "download_pipeline.yml"
-R is the repo, therefore nf-core/genomeassembler or nschan/genomeassembler etc. --ref is the branch from which you are using the action and --field specifies the branch you would like to test downloading.Matthias Zepper
02/11/2025, 4:44 PM.nextflow.log file available as artifact has not yet been rolled out. That should in the future make it easier to troubleshoot a failing pipeline.
To me the killed implies that the process may be terminated by the executor. Does the ASSEMBLE:HIFIASM module correctly implement the CPU/memory limits and are they also applied to the downloaded pipeline correctly e.g. with a correct config base?Matthias Zepper
02/11/2025, 4:46 PM- name: Upload Nextflow logfile for debugging purposes
uses: actions/upload-artifact@v4
with:
name: nextflow_logfile.txt
path: .nextflow.log*
include-hidden-files: trueNiklas Schandry
02/12/2025, 7:52 AMMatthias Zepper
02/12/2025, 8:22 AM