Age | Commit message (Collapse) | Author | Files | Lines |
|
Azure pipelines is removing python2 from the hostedtoolcache, see
https://github.com/actions/runner-images/issues/7401
We want to test that meson can still build modules for it, anyway.
|
|
[skip actions]
|
|
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
|
|
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.
|
|
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.
|
|
Which lets pytest understand unittest.subtest
|
|
|
|
|
|
See also: https://github.com/mesonbuild/meson/issues/9038#issuecomment-898960933
|
|
Propagate the run_tests.py exit code, rather than overwriting it with
the codecov exit code.
|
|
|
|
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.
|
|
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.
|
|
Which is used to validate the json schema files in the various test
directories in a unit test.
|
|
|
|
|
|
|