Use appveyor plugin for tox #1196
Conversation
Trying to avoid using {envsitepackagesdir} in tox.ini because of
tox-dev/tox#1191
Codecov Report
@@ Coverage Diff @@
## master #1196 +/- ##
=======================================
Coverage 83.79% 83.79%
=======================================
Files 18 18
Lines 2160 2160
=======================================
Hits 1810 1810
Misses 350 350Continue to review full report at Codecov.
|
|
That seems to be working. The Appveyor tests take a long, long time when they can't use the cached build of HDF5. I saw some warnings about missing executables on Travis, and figured out that tox was trying to run every configured Python interpreter to interpolate its site-packages dir into the config. So the later changes are working around that. |
|
@aragilar - it looks like you've done most of the work for Appveyor. Could I ask you to review this? The motivation is that I think warnings we're currently triggering in tox are due to turn into errors in a future version. |
|
This looks so much nicer now :) and yeah, appveyor is very slow. Thanks for chasing this up. |
Apparently the way we were setting TOXPYTHON for all environments is not recommended by the tox devs, and is probably going to raise an error in a future version of tox.
This is an attempt at making and using a plugin
tox-appveyorto select 32-bit or 64-bit Python builds on Appveyor.