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
Miscelaneous travis test failiures #2046
Comments
|
This is actually an easy one to fix. It should be using I like the idea of this "thread" though, so let's keep it open. |
https://travis-ci.org/matplotlib/matplotlib/jobs/7337969
Only showed up in 3.3 |
@mdboom I don't think the This is the error we get: import matplotlib.colorbar
File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/colorbar.py", line 36, in <module>
import matplotlib.contour as contour
File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/contour.py", line 27, in <module>
import matplotlib.texmanager as texmanager
File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/texmanager.py", line 89, in <module>
class TexManager:
File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/texmanager.py", line 124, in TexManager
mkdirs(texcache)
File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/cbook.py", line 1003, in mkdirs
os.makedirs(thispart, mode)
File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 17] File exists: '/tmp/matplotlib-vagrant' with v1.4.3. I can file a new issue if you prefer. I just used this as it was open already and related. |
@timj Can you make a new issue? That makes it easier to track. I am going to close this issue as until last month it had not been touched for 2 years. |
This issue is a bucket for test failures which have occurred on the travis tests, probably related to the fact that the tests are run in parallel.
I'm not unduly worried by these failures - it is something I'd like to fix, but not something which needs to hold up a release.
The problems will inevitably prove hard to reproduce and will be dependent on test execution order (which changes with hash ordering and performance of particular nodes).
The text was updated successfully, but these errors were encountered: