environment: # 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 interpreter # See: http://stackoverflow.com/a/13751649/163740 # 2018-01-19 PAK: probably irrelevant now that we are using tinycc rather than msvc #CMD_IN_ENV: "cmd /E:ON /V:ON /C obvci_appveyor_python_build_env.cmd" # Workaround for https://github.com/conda/conda-build/issues/636 PYTHONIOENCODING: "UTF-8" matrix: # Note: Because we have to separate the py2 and py3 components due to compiler version, we have a race condition for non-python packages. # Not sure how to resolve this, but maybe we should be tracking the VS version in the build string anyway? - TARGET_ARCH: "x86" CONDA_PY: "27" PY_CONDITION: "python >=2.7,<3" CONDA_INSTALL_LOCN: "C:\\Miniconda" # - TARGET_ARCH: "x86" # CONDA_PY: "34" # PY_CONDITION: "python >=3.4,<3.5" # CONDA_INSTALL_LOCN: "C:\\Miniconda3" - TARGET_ARCH: "x86" CONDA_PY: "35" PY_CONDITION: "python >=3.5,<3.6" CONDA_INSTALL_LOCN: "C:\\Miniconda35" - TARGET_ARCH: "x64" CONDA_PY: "27" PY_CONDITION: "python >=2.7,<3" CONDA_INSTALL_LOCN: "C:\\Miniconda-x64" # - TARGET_ARCH: "x64" # CONDA_PY: "34" # PY_CONDITION: "python >=3.4,<3.5" # CONDA_INSTALL_LOCN: "C:\\Miniconda3-x64" - TARGET_ARCH: "x64" CONDA_PY: "35" PY_CONDITION: "python >=3.5,<3.6" CONDA_INSTALL_LOCN: "C:\\Miniconda35-x64" # We always use a 64-bit machine, but can build x86 distributions # with the TARGET_ARCH variable (which is used by CMD_IN_ENV). platform: - x64 install: # Set the CONDA_NPY, although it has no impact on the actual build. # We need this because of a test within conda-build. - cmd: set CONDA_NPY=19 # Remove cygwin (and therefore the git that comes with it). # 2018-01-19 PAK: irrelevant since we already pulled the repo #- cmd: rmdir C:\cygwin /s /q # Set the conda path; would be nice to do this - cmd: path %CONDA_INSTALL_LOCN%\Scripts;%PATH% # Use the pre-installed Miniconda for the desired arch # # However, it is really old. So, we need to update some # things before we proceed. That seems to require it being # on the path. So, we temporarily put conda on the path # so that we can update it. Then we remove it so that # we can do a proper activation. - cmd: conda update --yes --quiet conda python - cmd: call %CONDA_INSTALL_LOCN%\Scripts\activate.bat #- cmd: conda config --add channels conda-forge #- cmd: conda config --set show_channel_urls true #- cmd: conda install --yes --quiet obvious-ci # 2018-01-19 PAK: skipping toolchain cython and cffi (these were for pyopencl?) - cmd: conda install --yes --quiet numpy scipy matplotlib docutils setuptools pytest # 2018-01-19 PAK: skipping pyopencl; this would be needed for deploy but maybe not for test #- cmd: conda install --yes --channel conda-forge pyopencl # 2018-01-19 PAK: 3rd party packages might need msvc, so %CMD_IN_ENV% may be needed for pip - cmd: pip install bumps unittest-xml-reporting tinycc build_script: # Build the project # 2018-01-19 PAK: maybe need one of this if using msvc? #- "%CMD_IN_ENV% python setup.py build" #- cmd /E:ON /V:ON /C obvci_appveyor_python_build_env.cmd python setup.py build - python setup.py build test_script: # Run the project tests # 2018-01-19 PAK: maybe need one of this if using msvc? #- "%CMD_IN_ENV% python -m sasmodels.model_test dll all" #- cmd /E:ON /V:ON /C obvci_appveyor_python_build_env.cmd python -m sasmoels.model_test dll all #- python -m sasmodels.model_test dll all #- nosetests -v sasmodels/*.py #- python -m pytest -v --cache-clear - python setup.py test --pytest-args -v