Again?

.github/workflows/pip-build.yml

@@ -45,7 +45,7 @@ jobs:
           - platform: "aarch64"
             docker-image: "meshlib/meshlib-ubuntu-arm64:mrbind-ci"
             container-options: "--user root"
-            runner: [ 'self-hosted', 'linux-arm64' ]
+            runner: linux-arm64
           - py-version: "3.8"
             py-tag: "cp38"
             py-cmd: "python3.8"
@@ -106,6 +106,7 @@ jobs:
 
       - name: Generate and build MRBind bindings
         run: |
+          free -h
           make -f scripts/mrbind/generate.mk -B --trace PACKAGE_NAME=meshlib CXX_FOR_ABI=/usr/bin/clang++-11 PYTHON_PKGCONF_NAME=python-${{matrix.py-version}}-embed
 
       - name: Run Tests
@@ -397,7 +398,9 @@ jobs:
         # `MACOS_MIN_VER` picked arbitrarily to match what Apple Clang uses when building MeshLib.
         # Not setting this or setting a different value cases a warning when linking the bindings, and you can get the correct (?) value from those warnings.
         run: |
-          make --version && make -f ./scripts/mrbind/generate.mk -B --trace PACKAGE_NAME=meshlib MACOS_MIN_VER=12.7 PYTHON_PKGCONF_NAME=python-${{matrix.py-version}}-embed EXTRA_CFLAGS='-DMB_PB11_ALLOW_STD_EXPECTED=0 -DMR_USE_STD_EXPECTED=0'
+          free -h
+          make --version
+          make -f ./scripts/mrbind/generate.mk -B --trace PACKAGE_NAME=meshlib MACOS_MIN_VER=12.7 PYTHON_PKGCONF_NAME=python-${{matrix.py-version}}-embed EXTRA_CFLAGS='-DMB_PB11_ALLOW_STD_EXPECTED=0 -DMR_USE_STD_EXPECTED=0'
 
       - name: Unit Tests
         # Using `cd` here fixes weird library loading issues.
@@ -436,7 +439,7 @@ jobs:
             container-options: "--user root"
             container-prefix: " "
           - platform: "aarch64"
-            runner: linux-arm64
+            runner: [ 'self-hosted', 'linux-arm64' ]
             container-options: "--user root"
             container-prefix: "arm64v8/"
           - os: "ubuntu:20.04"