From f007b4635bf32e8e752ad8eab849bf0694dbf81b Mon Sep 17 00:00:00 2001 From: Nick Mitchell Date: Wed, 18 Feb 2026 14:46:53 -0500 Subject: [PATCH] fix(ci): start ollama server manually when systemd is unavailable GHA runners don't always have systemd running, so the ollama install script silently fails to start the server. Start it manually if the API isn't already responding after install. Co-Authored-By: Claude Opus 4.6 Signed-off-by: Nick Mitchell --- .github/workflows/core.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.github/workflows/core.yml b/.github/workflows/core.yml index aeeca016..77a8c1d7 100644 --- a/.github/workflows/core.yml +++ b/.github/workflows/core.yml @@ -66,8 +66,9 @@ jobs: if [ "$RUNNER_OS" = "Linux" ]; then curl -fsSL https://ollama.com/install.sh | bash - # Wait for the server to actually be ready (install.sh starts it, but the - # "API is now available" message is printed before it accepts connections) + # systemd is not always running on GHA runners, so start manually if needed + curl -sf http://localhost:11434/api/tags > /dev/null 2>&1 || ollama serve & + # Wait for the server to actually be ready for i in $(seq 1 30); do curl -sf http://localhost:11434/api/tags > /dev/null 2>&1 && break [ "$i" = "30" ] && { echo "Ollama server failed to start"; exit 1; }