-
Notifications
You must be signed in to change notification settings - Fork 845
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
Fix AppVeyor and Travis UnitTests #636
Fix AppVeyor and Travis UnitTests #636
Conversation
This was the reason the travis python 2.7 was failing I believe. |
I think the python 2.7 build on travis-ci is failing because some tests (that are not executed for python 3.4) are now requiring pandas at build time (it was used to be optional). |
I'm fixing this as well, the X-display was on my VM so I just fixed it On Mon, Oct 12, 2015 at 10:30 AM, Riccardo Vianello <
|
the pandas version location changed in 0.17. We should use version not On Mon, Oct 12, 2015 at 11:43 AM, Brian Kelley fustigator@gmail.com wrote:
|
Pulled in riccardo's fix to make this a roll up for appveyor and travis builds. Cross your fingers! |
Yay! Appveyor is back to the land of the living :) Thanks @rvianello! |
…play Fix AppVeyor and Travis UnitTests
Thanks for tracking that down @bp-kelley! |
UnitTestSimilarityMaps was failing on travis because no XWindow display was set. This forces matplotlib to use the Agg renderer when the DISPLAY variable isn't set which allows the test to pass but perhaps has side-effects.