-
Notifications
You must be signed in to change notification settings - Fork 56
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
Ariba fails without --noclean depending on database #205
Comments
Could you send us the output of running
|
Yep no problem Running ARIBA on test data...|=============================================================================|
|
As a minor update I believe this could be the exact same issue as #203 |
Hitting this issue too. Did wonder whether it was due to the precarious set of packages I had installed, but in a clean conda python3.6 environment. Also getting this when building from github, or installation through brew: From the clean conda install:
|
I can't reproduce this bug, but could you confirm if you're using NFS? If so, maybe try on a different filesystem to confirm if it's only happening on NFS. I don't really have time to fix this in a nice way, so may just go for the ugly solution of replacing every shutil.rmtree with a call to rm -r. |
@martinghunt no, I saw the NFS ticket, but this is running on an EBS volume on an EC2 instance. On the root fs which is ext4. Running with --noclean does not help. I had a tmpdir specified to another ext4 partition above, but the behaviour was reproducible with tmpdir on the same partition |
I just put |
@martinghunt that does not fix my issue, however I've just run the same install procedure on an Ubuntu VM - effectively:
So the virtual env's should be similar, there were no 'historical' ariba install components kicking around. It fails on EC2, and works fine locally. So there's some environmental issue here I can't pin down. I will see if I can dig up any more reasoning behind this over the next few days if it is helpful. |
@martinghunt I'm sorry this was a false alarm. The only difference between the environments was really available memory. I was on a |
Closing this now as the issue is resolved. |
Recently updated ariba from 2.10.1 and noticed this issue emerge. Running on our installed resfinder DB has no issues however running others such as a mlst db or virulence finder leads to issues, see below). All mlst DBs were updated on Nov 23 (and custom ones added the clonal_complex) Adding the option for --noclean causes no errors to be generated.
The text was updated successfully, but these errors were encountered: