Hi all, I have previously used the chipseq pipeline (alongside atacseq and rnaseq) for a few years, but trying to run it on a new device, I cannot get the test run to terminate. It did the core analyses just fine, and I can see the results of the test run, but when it comes to the multiqc step, it got stuck for over thirty minutes and will not create the multiqc directory. I don't remember the multiqc step taking this long before, and I wanted to check if it's an issue. I am on a MacBook with an Apple M4 Pro processor, running Sequoia 15.3.1. Nextflow is on version 24.10.5, and I'm running the 2.1.0 release of the pipeline with the following line:

Nextflow run nf-core/chipseq --outdir nextflow-test -profile test,docker

Hi! Not sure if it could be a problem with #C07S9BW2STT architecture, maybe you can try with adding

arm

to your `-profile`s, @Maxime Garcia might be more helpful here though as TBH I have never used it

It's entirely possible, as Docker threw several exceptions before I could get the test run to work, but usually just adding -resume was enough without changing anything else. I tried terminating the multiqc step and running it again with -resume, but it hasn't fixed anything the first time.