aboutsummaryrefslogtreecommitdiff
path: root/ci
AgeCommit message (Collapse)AuthorFilesLines
2019-09-01azure: Bump to upstream ninja v1.9 releaseNirbheek Chauhan1-1/+8
2019-09-01azure: Download pkg-config.exe from meson cidataNirbheek Chauhan1-1/+1
2019-07-24ci: Fix failures in vs2019 jobs on AzureNirbheek Chauhan1-1/+1
pip warns about being out of date and powershell interprets that as an error because reasons. Found in https://github.com/mesonbuild/meson/pull/5687#issuecomment-514268525
2019-07-09Use pytest-xdist in Azure and Linux on Travis.Jussi Pakkanen1-0/+4
2019-06-06cmake: better loggingDaniel Mensinger1-0/+5
2019-04-20Merge pull request #5250 from jon-turney/test-compiler-reportJussi Pakkanen1-2/+2
Add a report of compilers used to run_project_tests.py
2019-04-16Add VS2019 backend CI and docs.Anton Kochkov1-1/+6
2019-04-15azure: Fix some places where an unexpected compiler is being picked upJon Turney1-2/+2
Now we have some information in CI logs about what compiler is actually being used, fix some places where an unexpected compiler is being picked up. Avoid picking up gcc-objc and gfortran from PATH in vs2017 image for VS test runs. Use clang for objc/objc++ in MSYS2 clang test runs, rather than picking up gcc from path. Also install gfortran for fortran tests on Cygwin.
2019-04-03d: Fix linker errors with shared libraries on WindowsAri Vuollet1-1/+1
2019-03-20Revert "azure: Don't try to publish logs from fork"Jon Turney1-2/+1
This reverts commit ec5e8869196cc7749f4c224bc8d850b33b942e2d.
2019-03-17azure: Unset BOOST_ROOT for Cygwin, MSYS2 and clang-clJon Turney1-0/+2
It looks like BOOST_ROOT is now set in the azure v2017 image (relevant change seems to be [1], pre-installing boost) Remove BOOST_ROOT from the environment to prevent attempting to use a boost which is incompatible with the compiler. (an MSVC boost should be compatible with clang-cl, but has problems, see c7a3e810) [1] https://github.com/Microsoft/azure-pipelines-image-generation/pull/732
2019-03-01azure: Fix python3 in vs2017 tasksDaniel Mensinger1-0/+7
2019-02-25ci: Debug why dmd --version is returning 1Nirbheek Chauhan1-1/+1
2018-11-27azure: ignore PRs which should be skipped for ciJon Turney1-1/+1
azure doesn't support [skip ci], so do nothing, rather than failing when we detect a PR which should have [skip ci], but didn't get skipped.
2018-11-21CI: port cygwin job from appveyor to azure-pipelinesChristoph Reiter2-28/+0
2018-11-16azure: Install Boost binaries for WindowsJon Turney1-0/+15
This installs a Boost distribution with built binaries for Windows, so we can have test coverage of both (i) boost components which are header-only libraries, and (ii) boost components which have separately-compiled libraries. (This duplicates the behaviour from appveyor of using Boost 1.64 with VS1027 (the first version which provides pre-built binaries for that), and Boost 1.60 for VS2015 (the oldest Boost provided by appveyor)) Don't install Boost when using clang-cl, as there appear to be issues in either Boost or clang-cl which prevent that from working well.
2018-11-16azure: Install the DMD D compilerJon Turney1-0/+14
Be more prescriptive about the static linker to use in test case common/143. This avoids using DMD's 'lib' in preference to clang-cl's 'llvm-lib' when both of them are in PATH
2018-11-16azure: Install x86 python in vs2015 image when building for x86Jon Turney1-1/+5
Use the x86 python when building for x86, to allow tests building python extension modules to work
2018-11-16azure: Add JDK installed in vs2015 image to PATHJon Turney1-1/+4
Add a JDK installed in vs2015 image to PATH, so java tests can be run JDK appear to be installed in several places, so we can always pick a different one: C:\java\jdk\jdk1.8.0_102\bin\ C:\Program Files\Java\jdk1.8.0_102\bin C:\Program Files (x86)\Java\jdk1.8.0_102\bin
2018-11-13azure: Simplify how we always publish test resultsJon Turney1-9/+2
Use a more concise way of always publishing test results, even when tests failed
2018-11-13azure: Enable vs2015 jobsJon Turney1-2/+5
Don't run MPI runtime installer, which fails with vs2015 image
2018-11-13azure: Install python3 for vs2015 imageJon Turney1-5/+14
We can't run the standard python installer on the vs2015 image, so we use an installation of chocolately python3 instead
2018-11-13azure: Rewrite importing visual studio environment variablesJon Turney1-6/+15
Rewrite this in a cruder way that doesn't require installing things (and so can work with the vs2015 image)
2018-11-04azure: Remove MSVC tools from PATH for clang-cl jobJon Turney1-2/+9
Add Windows SDK tools to PATH (for rc). This requires INCLUDE to be set. lld-link doesn't seem to default to searching the correct directories, so LIB needs to be set. The easiest way to get the correct setting of INLCUDE and LIB env vars seems to be to import the VS env vars, then revert the PATH.
2018-11-04azure: Add clang-cl/ninja to matrixJon Turney1-1/+15
Note that Vs2017 tools are also in PATH for llvm build
2018-10-16Don't try to publish logs from forkJon Turney1-0/+2
2018-10-14Set env vars so MS-MPI tests are runJon Turney1-0/+6
Import MS-MPI env vars set by installer in registry to environment Skip testing we can apply a version constraint to MPI when version isn't known (as is the case for MS-MPI) (These tests have never worked in appveyor)
2018-10-14Add resgen to PATH so csharp tests are runJon Turney1-0/+6
2018-10-14Add an azure-pipelines.ymlJon Turney1-0/+82
v1: Add an azure-pipelines.yml Don't check source line endings if autocrlf is on Handle origin-only refs in skip_ci Add .py to PATHEXT for the benefit of test_find_program() Publish logs as build artifacts and publish test results v2: Use .gitattributes to override autocrlf Move tmpdir, so it's not a subdir of source directory, otherwise it gets included in line-ending checks. Use serial build numbers, rather than date.dailybuildnumber Workaround for #3239 is no longer needed now a fix has been commited Tweak test results and artefact naming Wait for MS-MPI installers to complete Publish test results even if tests had an error
2018-09-21Appveyor: Install DMD compiler and dub packagesGoaLitiuM1-0/+71
[skip ci]
2018-01-06CI: Install gobject-introspection test prerequisites on CygwinJon Turney1-0/+3
2018-01-04CI: Run boost test for CygwinJon Turney1-2/+10
Also, use '^' to escape newlines in appveyor-install.bat to avoid an absurdly long line, remove some unnecessary quotation, and alphabetically sort packages Also, define the _XOPEN_SOURCE feature test macro in the boost test to avoid 'not declared in this scope' warnings for pthread_rwlock_init(), etc.
2017-09-28Revert "Add an additional Cygwin package repo with patched ninja"Jon Turney1-3/+1
This reverts commit 92c2bb75195c054dcdeae09f7d42393856a91748. This is no longer needed, as a patched ninja is now available from the standard Cygwin package repository, and prevents me from accidentally breaking CI when changing things in my personal package repository.
2017-09-18Revert "Revert "Merge pull request #1931 from centricular/use-patched-ninja""Nirbheek Chauhan1-1/+3
This reverts commit 5eb64a6f3e47b570f544524ef48dc6ef0e4dce59. Let's try again, with a fixed Ninja by QuLogic.
2017-07-18Revert "Merge pull request #1931 from centricular/use-patched-ninja"Jussi Pakkanen1-3/+1
This reverts commit aab7ada356e02033e4030143cf363d06d975283b, reversing changes made to e1b24765afd9e7d2d8043a408d69c7ad814d3551.
2017-07-17Add an additional Cygwin package repo with patched ninjaJon Turney1-1/+3
2017-05-21Enable code coverage on AppVeyor.Elliott Sales de Andrade1-1/+1
* Install pip on msys (which doesn't have it) * Install codecov/coverage everywhere. * Generate coverage XML file manually because codecov tries to call the coverage script itself and it's in a weird place on the path.
2017-05-21Use a wrapper script to run tests in Cygwin.Elliott Sales de Andrade2-6/+6
2017-04-07Add Cygwin/x86_64 to AppVeyor CI matrixJon Turney2-0/+17
Install ninja and packages needed for tests Don't bother with x86 for speed and reliability reasons
generated by cgit v1.1 at 2024-11-08 21:07:26 +0000