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
[ci] Pin Ollama to the AVX2 CPU build in the integration jobs (#904)
llama-server ships one libggml-cpu-<microarch> build per instruction set and loads the
best match for the host CPU at runtime. The hosted runner pool is mixed, so the kernels
that serve a request depend on the machine a job lands on, and jobs on the newer hosts
intermittently die with a llama-server segmentation fault (ollama/ollama#17006).
Remove the AVX-512-bearing builds after install so llama-server falls back to the AVX2
build, whose kernels every runner in the pool shares. Also log the runner CPU and the
remaining builds, so a future failure can be attributed to the microarchitecture that
served it.
Co-authored-by: weiqingy <ywqapply@gmail.com>
0 commit comments