-
Notifications
You must be signed in to change notification settings - Fork 10
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
Error running test again #82
Comments
Thanks for the quick reply, but my Windows laptop doesn't allow me to download it. I can't copy the link to the file either to download it directly in linux ... In the meantime, the first error was the following (I installed it in two machines, one of which is giving me the re-run error now, and the other has the same as before): make the black dots a little lighterAll the Hydra scaffolds have been identified in a connected component, continuing make the black dots a little lighterAll the BCnS_LGs scaffolds have been identified in a connected component, continuing make the black dots a little lighterQObject::killTimer: Timers cannot be stopped from another thread Removing output files of failed job plot_synteny_nocolor since they might be corrupted: Removing output files of failed job plot_synteny_of_ALGs_plus_species since they might be corrupted: |
Hi:
I ran the test_odp_basic, and I got an error in job 16 (unfortunately I didn't save it). I tried to run it again but I get the following error immediately, even after erasing the folders and files created in that first run:
Building DAG of jobs...
LockException:
Error: Directory cannot be locked. Please make sure that no other Snakemake process is trying to create the same files in the following directory:
/home/antonella/odp/tests/test_odp_basic
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.
I tried running ./test_odp_basic.sh --unlock
but the same happened (not sure if that's the way to do it).
Any help would be appreciated, thanks.
The text was updated successfully, but these errors were encountered: