-
Notifications
You must be signed in to change notification settings - Fork 0
/
appveyor.yml
37 lines (30 loc) · 1.31 KB
/
appveyor.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
# Environment loosely based on https://github.com/conda/conda/blob/master/appveyor.yml
environment:
global:
# SDK v7.0 MSVC Express 2008's SetEnv.cmd script will fail if the
# /E:ON and /V:ON options are not enabled in the batch script intepreter
# See: http://stackoverflow.com/a/13751649/163740
CMD_IN_ENV: "cmd /E:ON /V:ON /C .\\continuous_integration\\appveyor\\run_with_env.cmd"
matrix:
# Since appveyor is quite slow, we only use a single configuration
- PYTHON: "3.5"
ARCH: "64"
NUMPY: "1.12.1"
PANDAS: "0.19.2"
CONDA_ENV: testenv
init:
# Use AppVeyor's provided Miniconda: https://www.appveyor.com/docs/installed-software#python
- if "%ARCH%" == "64" set MINICONDA=C:\Miniconda35-x64
- if "%ARCH%" == "32" set MINICONDA=C:\Miniconda35
- set PATH=%MINICONDA%;%MINICONDA%/Scripts;%MINICONDA%/Library/bin;%PATH%
install:
# Update to a known good conda
# (to workaround http://help.appveyor.com/discussions/problems/4910)
- conda install -q -y conda=4.2.9
- continuous_integration\\appveyor\\setup_conda_environment.cmd
build_script:
- continuous_integration\\appveyor\\build.cmd
test_script:
# %CMD_IN_ENV% is needed for distutils/setuptools-based tests
# on certain build configurations.
- "%CMD_IN_ENV% continuous_integration\\appveyor\\run_tests.cmd"