From: Phillip Wood <phillip.wood123@gmail.com>
To: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] ci: add macOS jobs to GitLab CI
Date: Tue, 16 Jan 2024 14:58:53 +0000 [thread overview]
Message-ID: <61115e68-3d63-4e08-85f7-ae6650f3724e@gmail.com> (raw)
In-Reply-To: <d196cfd9d01fe3b52c75a1e4e0aca9f67567ab43.1705318985.git.ps@pks.im>
Hi Patrick
On 15/01/2024 11:45, Patrick Steinhardt wrote:
> Add two macOS-based jobs to GitLab CI, one for Clang and one for GCC.
This doesn't match whats in the rest of the commit message where you
explain why there is no gcc job. The patch itself looks good to me and
it is nice that we'll now be testing on arm64 with the GitLab runners.
> This matches equivalent jobs we have for GitHub Workflows, except that
> we use macOS 14 instead of macOS 13.
>
> Note that one test marked as `test_must_fail` is surprisingly passing:
>
> t7815-grep-binary.sh (Wstat: 0 Tests: 22 Failed: 0)
> TODO passed: 12
>
> This seems to boil down to an unexpected difference in how regcomp(1)
nit: regcomp(3)?
Best Wishes
Phillip
> works when matching NUL bytes. Cross-checking with the respective GitHub
> job shows though that this is not an issue unique to the GitLab CI job
> as it passes in the same way there.
>
> Further note that we do not include the equivalent for the "osx-gcc" job
> that we use with GitHub Workflows. This is because the runner for macOS
> on GitLab is running on Apple M1 machines and thus uses the "arm64"
> architecture. GCC does not support this platform yet.
>
> Signed-off-by: Patrick Steinhardt <ps@pks.im>
> ---
> .gitlab-ci.yml | 26 +++++++++++++++++++++++++-
> ci/lib.sh | 9 ++++++++-
> 2 files changed, 33 insertions(+), 2 deletions(-)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 793243421c..9748970798 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -7,7 +7,7 @@ workflow:
> - if: $CI_COMMIT_TAG
> - if: $CI_COMMIT_REF_PROTECTED == "true"
>
> -test:
> +test:linux:
> image: $image
> before_script:
> - ./ci/install-docker-dependencies.sh
> @@ -52,6 +52,30 @@ test:
> - t/failed-test-artifacts
> when: on_failure
>
> +test:osx:
> + image: $image
> + tags:
> + - saas-macos-medium-m1
> + before_script:
> + - ./ci/install-dependencies.sh
> + script:
> + - ./ci/run-build-and-tests.sh
> + after_script:
> + - |
> + if test "$CI_JOB_STATUS" != 'success'
> + then
> + ./ci/print-test-failures.sh
> + fi
> + parallel:
> + matrix:
> + - jobname: osx-clang
> + image: macos-13-xcode-14
> + CC: clang
> + artifacts:
> + paths:
> + - t/failed-test-artifacts
> + when: on_failure
> +
> static-analysis:
> image: ubuntu:22.04
> variables:
> diff --git a/ci/lib.sh b/ci/lib.sh
> index f631206a44..d5dd2f2697 100755
> --- a/ci/lib.sh
> +++ b/ci/lib.sh
> @@ -252,7 +252,14 @@ then
> CI_COMMIT="$CI_COMMIT_SHA"
> case "$CI_JOB_IMAGE" in
> macos-*)
> - CI_OS_NAME=osx;;
> + # GitLab CI has Python installed via multiple package managers,
> + # most notably via asdf and Homebrew. Ensure that our builds
> + # pick up the Homebrew one by prepending it to our PATH as the
> + # asdf one breaks tests.
> + export PATH="$(brew --prefix)/bin:$PATH"
> +
> + CI_OS_NAME=osx
> + ;;
> alpine:*|fedora:*|ubuntu:*)
> CI_OS_NAME=linux;;
> *)
next prev parent reply other threads:[~2024-01-16 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 11:44 [PATCH 0/3] ci: add support for macOS to GitLab CI Patrick Steinhardt
2024-01-15 11:44 ` [PATCH 1/3] ci: make p4 setup on macOS more robust Patrick Steinhardt
2024-01-18 7:19 ` Matthias Aßhauer
2024-01-18 9:44 ` Patrick Steinhardt
2024-01-15 11:45 ` [PATCH 2/3] Makefile: detect new Homebrew location for ARM-based Macs Patrick Steinhardt
2024-01-15 11:45 ` [PATCH 3/3] ci: add macOS jobs to GitLab CI Patrick Steinhardt
2024-01-16 14:58 ` Phillip Wood [this message]
2024-01-17 7:34 ` Patrick Steinhardt
2024-01-18 10:22 ` [PATCH v2 0/5] ci: add support for macOS " Patrick Steinhardt
2024-01-18 10:22 ` [PATCH v2 1/5] t7527: decrease likelihood of racing with fsmonitor daemon Patrick Steinhardt
2024-01-18 10:22 ` [PATCH v2 2/5] Makefile: detect new Homebrew location for ARM-based Macs Patrick Steinhardt
2024-01-18 10:22 ` [PATCH v2 3/5] ci: handle TEST_OUTPUT_DIRECTORY when printing test failures Patrick Steinhardt
2024-01-18 10:22 ` [PATCH v2 4/5] ci: make p4 setup on macOS more robust Patrick Steinhardt
2024-01-18 10:23 ` [PATCH v2 5/5] ci: add macOS jobs to GitLab CI Patrick Steinhardt
2024-01-21 14:50 ` [PATCH v2 0/5] ci: add support for macOS " Phillip Wood
2024-01-22 6:14 ` Patrick Steinhardt
2024-01-22 15:44 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61115e68-3d63-4e08-85f7-ae6650f3724e@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).