Age | Commit message (Collapse) | Author | Files | Lines |
|
The job is taking too long and timing out, use pytest-xdist to speed
up unit tests. Speeds it up on my system from 20 min to 8 min.
Still much slower than native windows: vs2017-x64 takes 3.5 min with
pytest-xdist.
|
|
|
|
|
|
Add a report of compilers used to run_project_tests.py
|
|
|
|
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.
|
|
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
|
|
|
|
|
|
|
|
The package has been moved from python3-pip to python3N-pip where N is
5, 6, 7. We use Python 3.5, so let's use that.
|
|
msys2 now has ninja 1.9.0 which includes the timestamp fixes
|
|
The clang package depends on the gcc package, so we need to explicitly
select the compiler (as the priority order built into meson will prefer
gcc to clang)
v2:
ensure $(MSYS2-ARCH)-pkg-config is installed
|
|
Recent test changes depend on cmake being available.
|
|
|
|
|
|
|
|
Default is unlimited, not 1
|
|
|
|
Don't run MPI runtime installer, which fails with vs2015 image
|
|
Note that Vs2017 tools are also in PATH for llvm build
|
|
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
|