Zengtudor/pybind11
1
0
Fork 0
mirror of https://github.com/pybind/pybind11.git synced 2024-11-11 16:13:53 +00:00
Code Issues Packages Projects Releases Wiki Activity
68bee938de
pybind11/.appveyor.yml

41 lines
1.3 KiB
YAML
Raw Normal View History

appveyor CI script
2015-10-18 15:04:24 +00:00
version: 1.0.{build}
Add VS 2017 build, and bump conda to 3.6 This adds VS 2017 to the build matrix, plus various other small appveyor build changes: - conda version bumped from 3.5 to 3.6 - build newer versions/architectures/python first (i.e. VS2017/x64/3.6 is the first build, VS2015/x86/2.7 is the last) - stop building after a job failure: often a build failure in one occurs everywhere; this just stops processing jobs (freeing them up for other PRs) if an error is hit. Annoyingly, appveyor doesn't allow excluding tests: i.e. the test matrix is always dense (appveyor issue 386), so for now we'll just run everything. (Once appveyor issue 386 is resolved, we can come back and cut this down to 4-5 builds).
2017-03-12 03:03:23 +00:00
image:
- Visual Studio 2015
disabling AppVeyor (for this PR)
2020-11-20 20:53:52 +00:00
branches:
only:
- will_never_exist
appveyor: legacy build on win32
2015-10-23 08:21:09 +00:00
test: off
fixed regression in STL type caster RVPs (fixes #1561) (#1603)
2018-11-09 19:12:46 +00:00
skip_branch_with_pr: true
AppVeyor: use parallel builds My group now has a subscription to AppVeyor pro, which also permits running parallel builds on the open source projects.
2017-04-05 15:02:34 +00:00
build:
parallel: true
Improve CI test coverage: eigen, numpy and C++14
2016-07-29 22:15:01 +00:00
platform:
Add VS 2017 build, and bump conda to 3.6 This adds VS 2017 to the build matrix, plus various other small appveyor build changes: - conda version bumped from 3.5 to 3.6 - build newer versions/architectures/python first (i.e. VS2017/x64/3.6 is the first build, VS2015/x86/2.7 is the last) - stop building after a job failure: often a build failure in one occurs everywhere; this just stops processing jobs (freeing them up for other PRs) if an error is hit. Annoyingly, appveyor doesn't allow excluding tests: i.e. the test matrix is always dense (appveyor issue 386), so for now we'll just run everything. (Once appveyor issue 386 is resolved, we can come back and cut this down to 4-5 builds).
2017-03-12 03:03:23 +00:00
- x86
appveyor: legacy build on win32
2015-10-23 08:21:09 +00:00
environment:
matrix:
Speed up AppVeyor build (#1021) The `latest` build remains as is, but all others are modified to: * Use regular Python instead of conda. `pip install` is much faster than conda, but scipy isn't available. Numpy is still tested. * Compile in debug mode instead of release. * Skip CMake build tests. For some reason, CMake configuration is very slow on AppVeyor and these tests are almost entirely CMake. The changes reduce build time to about 1/3 of the original. The `latest` config still covers scipy, release mode and the CMake build tests, so the others don't need to.
2017-08-23 15:18:57 +00:00
- PYTHON: 36
CONFIG: Debug
- PYTHON: 27
CONFIG: Debug
appveyor CI script
2015-10-18 15:04:24 +00:00
install:
Improve CI test coverage: eigen, numpy and C++14
2016-07-29 22:15:01 +00:00
- ps: |
ci: trim down Appveyor
2020-07-26 15:43:56 +00:00
$env:CMAKE_GENERATOR = "Visual Studio 14 2015"
if ($env:PLATFORM -eq "x64") { $env:PYTHON = "$env:PYTHON-x64" }
$env:PATH = "C:\Python$env:PYTHON\;C:\Python$env:PYTHON\Scripts\;$env:PATH"
python -W ignore -m pip install --upgrade pip wheel
chore: add pytest-timeout, mypy
2021-01-27 00:25:35 +00:00
python -W ignore -m pip install pytest numpy --no-warn-script-location pytest-timeout
Improve CI test coverage: eigen, numpy and C++14
2016-07-29 22:15:01 +00:00
- ps: |
ci: Eigen moved
2020-09-03 16:47:30 +00:00
Start-FileDownload 'https://gitlab.com/libeigen/eigen/-/archive/3.3.7/eigen-3.3.7.zip'
7z x eigen-3.3.7.zip -y > $null
$env:CMAKE_INCLUDE_PATH = "eigen-3.3.7;$env:CMAKE_INCLUDE_PATH"
appveyor CI script
2015-10-18 15:04:24 +00:00
build_script:
Add Catch framework for testing embedding support and C++-side features At this point, there is only a single test for interpreter basics. Apart from embedding itself, having a C++ test framework will also benefit the C++-side features by allowing them to be tested directly.
2017-03-23 16:27:32 +00:00
- cmake -G "%CMAKE_GENERATOR%" -A "%CMAKE_ARCH%"
fix: address review points from @YannickJadoul
2020-07-29 19:02:53 +00:00
-DCMAKE_CXX_STANDARD=14
Add Catch framework for testing embedding support and C++-side features At this point, there is only a single test for interpreter basics. Apart from embedding itself, having a C++ test framework will also benefit the C++-side features by allowing them to be tested directly.
2017-03-23 16:27:32 +00:00
-DPYBIND11_WERROR=ON
-DDOWNLOAD_CATCH=ON
-DCMAKE_SUPPRESS_REGENERATION=1
CI fixes (#1744) * Fix warning that not including a cmake source or build dir will be a fatal error (it is now on newest CMakes) * Fixes appveyor * Travis uses CMake 3.9 for more than a year now * Travis dropped sudo: false in December * Dropping Sphinx 2 - clang7: Suppress self-assign warnings; fix missing virtual dtors - pypy: - Keep old version (newer stuff breaks) - Pin packages to extra index for speed - travis: - Make docker explicit; remove docker if not needed - Make commands more verbose (for debugging / repro) - Make Ubuntu dist explicit per job - Fix Windows - Add names to travis
2019-04-06 17:09:39 +00:00
.
Improve CI test coverage: eigen, numpy and C++14
2016-07-29 22:15:01 +00:00
- set MSBuildLogger="C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"
Speed up AppVeyor build (#1021) The `latest` build remains as is, but all others are modified to: * Use regular Python instead of conda. `pip install` is much faster than conda, but scipy isn't available. Numpy is still tested. * Compile in debug mode instead of release. * Skip CMake build tests. For some reason, CMake configuration is very slow on AppVeyor and these tests are almost entirely CMake. The changes reduce build time to about 1/3 of the original. The `latest` config still covers scipy, release mode and the CMake build tests, so the others don't need to.
2017-08-23 15:18:57 +00:00
- cmake --build . --config %CONFIG% --target pytest -- /m /v:m /logger:%MSBuildLogger%
- cmake --build . --config %CONFIG% --target cpptest -- /m /v:m /logger:%MSBuildLogger%
Add Catch framework for testing embedding support and C++-side features At this point, there is only a single test for interpreter basics. Apart from embedding itself, having a C++ test framework will also benefit the C++-side features by allowing them to be tested directly.
2017-03-23 16:27:32 +00:00
on_failure: if exist "tests\test_cmake_build" type tests\test_cmake_build\*.log*
Reference in New Issue Copy Permalink