ci: add a runner for macos
authorMatt Harbison <matt_harbison@yahoo.com>
Tue, 08 Oct 2024 18:59:44 -0400
changeset 52014 941141c2c475
parent 52013 5713adc51f2a
child 52015 f9f41b3dcb64
ci: add a runner for macos This is running from a venv, created with the packages from the requirements file in the `test-setup-future-work` topic being discussed separately. We can basically reuse the existing `test_c` configuration as-is, but there was one small issue- if the clone from the previous CI run is still present in `/tmp`, the clone for the current run fails. It's not a problem for the current setup because a new container is instantiated, so the easy fix is to simply delete the clone first. (The Windows CI avoids this by not cloning in the first place.) It looks like it takes ~80m to run the whole test suite on the current system.
contrib/heptapod-ci.yml
--- a/contrib/heptapod-ci.yml	Tue Oct 15 13:52:21 2024 +0200
+++ b/contrib/heptapod-ci.yml	Tue Oct 08 18:59:44 2024 -0400
@@ -41,6 +41,7 @@
     before_script:
       - echo "python used, $PYTHON"
       - for tool in $SHOW_VERSION_OF ; do echo '#' version of $tool; $tool --version; done
+      - rm -rf /tmp/mercurial-ci/  # Clean slate if not using containers
       - hg clone . /tmp/mercurial-ci/ --noupdate --config phases.publish=no
       - hg -R /tmp/mercurial-ci/ update `hg log --rev '.' --template '{node}'`
       - cd /tmp/mercurial-ci/
@@ -179,3 +180,8 @@
     variables:
         RUNTEST_ARGS: "--blacklist C:/Temp/check-tests.txt --pyoxidized"
         PYTHON: py -3
+
+macos:
+    <<: *test_c
+    tags:
+      - macos