| Age | Commit message (Collapse) | Author |
|---|
|
This is fixed in Ubuntu rolling now and Bionic wasn't affected to
begin with.
Bug: https://bugs.debian.org/1078026
|
|
It is genuinely horribly buggy so we don't want the testsuite to
succeed. We make a special exception for the CI runner since it is a
known breakage but people packaging meson should see the issue.
|
|
The pkgconfig file in Debian and Ubuntu is definitely broken and we've
reported it upstream, but we don't really want to keep our image building
failing while we wait for that to be fixed.
Skip the auto/pkgconfig test if both: a) we're on Ubuntu, and b) the .pc
checksum matches a known-bad copy. I'm also CC'd to the bug to catch if it
gets fixed.
Bug: https://bugs.debian.org/1078026
|
|
expect_skip_on_os
The test.json format currently has three keys related to skipping tests:
* `skip_on_jobname`
* `skip_on_os`
* `skip_on_env`
While `skip_on_env` marks the test itself as skipped, i.e. they don't get run when the
conditions are met, the other two skip options are just marking the test as "expected to be skipped"
if the conditions apply, i.e. they want to see `MESON_SKIP_TEST` in the output and things will
fail if that doesn't happen. They don't actually skip the tests as the names imply.
To make this clearer rename the keys:
* `skip_on_jobname` -> `expect_skip_on_jobname`
* `skip_on_os` -> `expect_skip_on_os`
`skip_on_env` stays the same, since that actually skips.
The docs were also confused about this, so adjust that too.
|
|
|
|
Remove hard-coded framework test skip logic in skippable(), instead
annotate test.json with environments in which skip is expected.
(Mainly this is done with by testing the value of MESON_CI_JOBNAME now
set for linux jobs)
|
|
|
|
This is a nice way to ensure that all of the methods continue to work
|
|
So we can force the use of pkg-config or config-tool
|
|
|
|
|
|
|
|
|
|
While this isn't solved everywhere, this seems reasonable to disable it.
Signed-off-by: Alexis Jeandet <alexis.jeandet@member.fsf.org>
|
|
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)
|
|
Use the 'CI' environment variable to detect CI environment, rather than a
collection of CI-specific ones.
|
|
|
|
|
|
|
|
|
|
This prevents them being cross-compiled (which wouldn't work without MPI
cross-compilers) and disables Windows builds (will need to be fixed
later.)
|
