-
Notifications
You must be signed in to change notification settings - Fork 86
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
Exception: Cannot locate xUnit report / IOError: [Errno 21] Is a directory #946
Comments
Same error+exception happening when running locally (planemo test on galaxy dev branch). No issue when running on release_19.05. I tried removing *pyc files as per #724 (comment) - which did not fix it. I'm looking into it... |
Here's why the IOError happens: I don't have a solution yet, but I should have one soon. ping @natefoo : I believe the following commit is 3 years old, but was only recently merged, which is why the issue never surfaced? galaxyproject/galaxy@280d2e3#diff-849c0107be4d923c00577caf4f84a1c5R38 |
@ic4f yeah that was part of the 4-year-old installable Galaxy PR. |
Partial solution to galaxyproject#946 (first attempt)
I cannot reproduce the xUnit error anymore (running on a Mac, Planemo runs on python 2.7.10 and 3.7.3; Galaxy on 2.7.10, dev branch. I tried both existing installs (with --galaxy_root) and a clean install; in all cases I did not switch branches). I only see a bad file descriptor error, which is not really a thing (discussed here: #752). On a side note, the twobit.loc error (#679), which was present, has disappeared too. @jmchilton I don't know Planemo well enough to dig any deeper at this point, so I'm leaving this as is. Tests run (at least on my machine). |
Also failing on my MIRA repository, with a weekly cron test, see: https://travis-ci.org/peterjc/galaxy_mira/builds e.g. 2 months ago passed: https://travis-ci.org/peterjc/galaxy_mira/builds/552876215 The next week it failed: https://travis-ci.org/peterjc/galaxy_mira/builds/555897289 There doesn't seem to be an easy way to get the date from a TravisCI build... |
Like #724, but the circumstantial evidence points are a different root cause:
See the following TravisCI tests from the same tool commit peterjc/galaxy_blast@3095f19 run as TravisCI cron jobs:
The text was updated successfully, but these errors were encountered: