Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
P
pybind11
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
open
pybind11
Commits
4c72ec22
Commit
4c72ec22
authored
Apr 09, 2017
by
Jason Rhinelander
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Appveyor: Remove /m to attempt to resolve build failures
/m also doesn't seem to have made the builds any faster.
parent
e9e17746
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
.appveyor.yml
+2
-2
No files found.
.appveyor.yml
View file @
4c72ec22
...
@@ -40,6 +40,6 @@ install:
...
@@ -40,6 +40,6 @@ install:
build_script
:
build_script
:
-
cmake -G "%CMAKE_GENERATOR%" -A "%CMAKE_ARCH%" -DPYBIND11_WERROR=ON
-
cmake -G "%CMAKE_GENERATOR%" -A "%CMAKE_ARCH%" -DPYBIND11_WERROR=ON
-
set MSBuildLogger="C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"
-
set MSBuildLogger="C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"
-
cmake --build . --config Release --target pytest -- /v:m /
m /
logger:%MSBuildLogger%
-
cmake --build . --config Release --target pytest -- /v:m /logger:%MSBuildLogger%
-
cmake --build . --config Release --target test_cmake_build -- /v:m /
m /
logger:%MSBuildLogger%
-
cmake --build . --config Release --target test_cmake_build -- /v:m /logger:%MSBuildLogger%
on_failure
:
if exist "tests\test_cmake_build" type tests\test_cmake_build\*.log
on_failure
:
if exist "tests\test_cmake_build" type tests\test_cmake_build\*.log
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment