-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest template merge completely broke dev branch (on AWS + Fusion) #392
Comments
Have you tried simplifying the names to just The sample name doesn't have to match the original input, you can name it something more descriptive than an ID as well. |
I have a feeling this might be it, with the soft links for whatever weird reason. Two new experiments:
Also, any previous versions confirmed? Because the trimgalore module hasn't been updated in 11 months. |
It also fails with ln: GSM7506206.fastq.gz: File exists
ln: GSM7506206.fastq.gz: File exists
ln: GSM7506206.fastq.gz: File exists
ln: GSM7506206.fastq.gz: File exists
ln: GSM7506206.fastq.gz: File exists and the process doesn't start at all with Execution completed unsuccessfully!
The full error message was:
fromIndex = -1 |
test(#392): Add boilerplate for tests
Description of the bug
I am trying to launch a methylseq run using the latest
dev
branch where some (but not a all) samples require merging of technical replicates before launching. If I understand it correctly, the latest template changes were merged into dev earlier this month, but something seems to have gone awry:Within seconds of launching the run, I observe the following errors:
bismark2summary
is run, and obviously fails...Obviously, the
ln -s
command attempts to use the very same filename 6 times over, which doesn't work. But something also screwed up the entire workflow logic, i.e. not starting with merging, and instead running post-run QC right at the start.Here is an example samplesheet:
Command used and terminal output
Relevant files
No response
System information
I am running this on Seqera platform on AWS, using Fusion. Nextflow v23.10.1 build 5891. nf-core/methylseq version:
dev
The text was updated successfully, but these errors were encountered: