aboutsummaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2022-01-31 15:59:16 -0500
committerNirbheek Chauhan <nirbheek.chauhan@gmail.com>2022-02-14 14:46:01 +0530
commit4274e0f42a9673df981dd7a7a456f4d4fcfe5452 (patch)
tree3f4268b357091f243785ca9c2e88ebf6ad6e3a94 /.github
parent37be39bc69789a7b2cb9415ca61e0ce4209dc666 (diff)
downloadmeson-4274e0f42a9673df981dd7a7a456f4d4fcfe5452.zip
meson-4274e0f42a9673df981dd7a7a456f4d4fcfe5452.tar.gz
meson-4274e0f42a9673df981dd7a7a456f4d4fcfe5452.tar.bz2
unittests: fine-tune the check for whether we are in CI
The $CI environment variable may be generally set by Github or Gitlab actions, and is not a reliable indicator of whether we are running "CI". It could also, for an absolutely random example that didn't *just happen*, be Alpine Linux's attempt to enable the Meson testsuite in their packaging, which... uses Gitlab CI. In this case, we do want to perform normal skipping on not-found requirements. Instead of checking for $CI, check for $MESON_CI_JOBNAME as we already use that in all of our own CI jobs for various reasons. This makes it easier for linux distros to package Meson without accumulating hacks like "run the testsuite using `env -u CI`".
Diffstat (limited to '.github')
-rw-r--r--.github/workflows/macos.yml1
1 files changed, 1 insertions, 0 deletions
diff --git a/.github/workflows/macos.yml b/.github/workflows/macos.yml
index d60244b..8b60b75 100644
--- a/.github/workflows/macos.yml
+++ b/.github/workflows/macos.yml
@@ -35,6 +35,7 @@ jobs:
- env:
CPPFLAGS: "-I/usr/local/include"
LDFLAGS: "-L/usr/local/lib"
+ MESON_CI_JOBNAME: unittests-appleclang
MESON_UNIT_TEST_BACKEND: ninja
# These cannot evaluate anything, so we cannot set PATH or SDKROOT here
run: |