You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, Snakemake will not let me unlock the directory.
I am running snakemake --unlock, but I'm still getting this when I run the drop pipeline:
check for missing R packages
Structuring dependencies...
Dependencies file generated.
Building DAG of jobs...
Unlocking working directory.
check for missing R packages
Structuring dependencies...
Dependencies file generated.
Building DAG of jobs...
Executing subworkflow AE.
Structuring dependencies...
Dependencies file generated.
Building DAG of jobs...
Error: Directory cannot be locked. Please make sure that no other Snakemake process is trying to create the same files in the following directory:
/gpfs/scratch/evrong01/droptest/.drop/modules/aberrant-expression-pipeline
If you are sure that no other instances of snakemake are running on this directory, the remaining lock was likely caused by a kill signal or a power loss. It can be removed with the --unlock argument.
The text was updated successfully, but these errors were encountered:
Hi, Snakemake will not let me unlock the directory.
I am running snakemake --unlock, but I'm still getting this when I run the drop pipeline:
check for missing R packages
Structuring dependencies...
Dependencies file generated.
Building DAG of jobs...
Unlocking working directory.
check for missing R packages
Structuring dependencies...
Dependencies file generated.
Building DAG of jobs...
Executing subworkflow AE.
Structuring dependencies...
Dependencies file generated.
Building DAG of jobs...
Error: Directory cannot be locked. Please make sure that no other Snakemake process is trying to create the same files in the following directory:
/gpfs/scratch/evrong01/droptest/.drop/modules/aberrant-expression-pipeline
If you are sure that no other instances of snakemake are running on this directory, the remaining lock was likely caused by a kill signal or a power loss. It can be removed with the --unlock argument.
The text was updated successfully, but these errors were encountered: