Age | Commit message (Collapse) | Author | Files | Lines |
|
I would like to use the same pattern rule as github actions uses:
'[0-9]+.[0-9]+'
But azure pipelines doesn't document what the syntax here is, and it
scares me that perhaps the reason we didn't already do this is because
it doesn't work at all.
|
|
|
|
The coverage report was always the final section of the main test run.
This made it hard to scroll around and find exactly what went wrong --
particularly as not everyone realizes that coverage isn't part of the
test run, but also because the output from coverage is... excessively
long.
This mirrors what we do in our other workflows.
|
|
The Windows 2016 images have been deprecated for a while now and
regularly browning out. There's no viable replacement for testing that
we can generate a usable `--backend=vs2017` project, so we cannot
migrate this to anything else.
The deprecated images are finally fully removed. See
https://github.com/actions/virtual-environments/issues/5403
And now we get universal red CI, we cannot just wait for the brownout to
end to get a tiny little bit of final testing.
Simply remove the jobs so that we can tell if all the CI that actually
runs, is passing.
|
|
This enables the fortran tests for Azure.
We only test on x64, because:
- ifort isn't arm64 compatible
- x86 may in theory exist, but Meson reports it cannot compile
executables
|
|
Comment out the pending deprecation notice. It cannot be reached
anymore, but is still useful for the next time we do a version bump.
|
|
This also removes the additional upload step for test results
in the hope of fixing the `autoCancel` flag.
|
|
|
|
This restricts the pipeline from running on 'non-code' pushes and PRs in
the same way that GitHub workflows which run project tests are (although
the syntax is different, and must be made more explicit as wildcards
aren't supported).
|
|
|
|
* CI: Don't run cross-only test when other workflows are changed
* CI: Move Cygwin test run from Azure Pipelines to GitHub workflow
Also review installed package list, dropping detritus from 42792554, not
removed in f5ed85d7.
|
|
This reverts commit dce60c8f58798e0457a9bb24198adb039a0e6fdd.
|
|
Python3 in Cygwin is now Python 3.8
|
|
This uses the msys2/setup-msys2@v2 to set up MSYS2
|
|
|
|
|
|
This should use the package database from the installer,
from the release choco provides and result in fewer potential
changes overall.
|
|
Add a cross-file for MSVC UWP ARM64.
Bump cidata tag to get an updated install.ps1 script (run by run.ps1)
which sets the vcvars environment correctly when cross-compiling.
Since arranging the correct environment for simultaneous cross and
native 'cl' use is hard, this is test run uses '--cross-only' so we
don't require a native compiler.
Extend '--cross-only' so it also explicitly uses a machine file which
makes all build machine compilers unusable.
|
|
Fixes breakage when installing psutil:
Collecting psutil>=3.0.0
Downloading psutil-5.7.2.tar.gz (460 kB)
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/cygdrive/c/Users/VSSADM~1/AppData/Local/Temp/pip-install-dajoe3xd/psutil/setup.py'"'"'; __file__='"'"'/cygdrive/c/Users/VSSADM~1/AppData/Local/Temp/pip-install-dajoe3xd/psutil/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base '/cygdrive/c/Users/VSSADM~1/AppData/Local/Temp/pip-pip-egg-info-1ei2_y44'
cwd: /cygdrive/c/Users/VSSADM~1/AppData/Local/Temp/pip-install-dajoe3xd/psutil/
Complete output (1 lines):
platform cygwin is not supported
|
|
vc2017x64vs and vc2019x64vs sometimes timeout because they exceed the
60 min default limit.
|
|
Also kill all MSYS2 processes after the first update, and constantly
print update status.
|
|
The default timeout is 60 min and we're timing out, but the maximum we
can have is 6 hours. Bump it to 120 min for now.
|
|
|
|
|
|
|
|
It's one of the causes of the cmake test failures, and it's also
plaguing the VS2019 jobs now because of the image update.
|
|
These only fail when building with msvc/clang-cl on the VS2017-Win2016
image. See: https://github.com/mesonbuild/meson/issues/7307
|
|
|
|
|
|
Which is used to validate the json schema files in the various test
directories in a unit test.
|
|
This reverts commit 5f9dccb9bce957979efa6efea961192a12f76790.
|
|
This was dropped when the VS2015 images were removed from Azure.
|
|
|
|
|
|
Adds a CI dependency on the `pefile` python module.
|
|
|
|
actions: run if .yml itself changed
|
|
|
|
|
|
Install python[23]-devel packages on Cygwin, so that python tests which
require that can run.
(Only the default version of python (currently 3.6) provides the
/usr/lib/pkgconfig/python3.pc file we are looking for so also update to
that version)
|
|
Compiler version is hard-coded so that we remember to revisit this
when the GCC version is updated.
Closes https://github.com/mesonbuild/meson/issues/5807
|
|
The high-res timestamp PR by QuLogic was merged in v1.9, so we can
switch back to upstream ninja.
|
|
|
|
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.
|