You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Test on self-hosted mac
* Automatically add pipx apps to PATH
* Test all MLIPs on mac
* Remove pipx and poetry installation
* Fix poetry path
* Update MacOS ci for uv
* Fix coveralls
* Update docs for self-hosted runners
General instructions for setting up self-hosted GitHub runners can be found `here <https://docs.github.com/en/actions/hosting-your-own-runners>`_.
6
+
7
+
This process typically involves:
8
+
9
+
1. Add a new self-hosted runner on GitHub
10
+
2. Run instructions from GitHub on your runner to download and configure
11
+
3. Ensure tags added to the runner are unique, and match those in ``runs-on`` within the CI workflow
12
+
13
+
14
+
MacOS self-hosted runner
15
+
========================
16
+
17
+
Currently, ``janus-core`` uses a self-hosted runner to run all unit tests on MacOS.
18
+
19
+
To ensure the self-hosted runner remains active, we currently recommend using
20
+
21
+
.. code-block:: bash
22
+
23
+
nohup ./run.sh &!
24
+
25
+
This runs the script in the background, and disowns the process, allowing the ssh connection to be ended without killing the process.
26
+
27
+
It would be preferable to `configure the runner application as a service <https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service?platform=mac>`_,
28
+
but currently this appears to lead to difficulties if the GUI is not active
29
+
and/or ``sudo`` permissions are not used in running the service.
0 commit comments