From f0a351810c496d6ead14b3d3a9d4d536c4ae772a Mon Sep 17 00:00:00 2001 From: Daniel Hiltgen Date: Fri, 22 Nov 2024 08:05:45 -0800 Subject: [PATCH] tests: fix max queue integration test (#7782) This had fallen out of sync with the envconfig behavior, where max queue default was not zero. --- integration/max_queue_test.go | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/integration/max_queue_test.go b/integration/max_queue_test.go index ec9e085a..a2766430 100644 --- a/integration/max_queue_test.go +++ b/integration/max_queue_test.go @@ -16,7 +16,6 @@ import ( "github.com/stretchr/testify/require" "github.com/ollama/ollama/api" - "github.com/ollama/ollama/envconfig" ) func TestMaxQueue(t *testing.T) { @@ -27,12 +26,8 @@ func TestMaxQueue(t *testing.T) { // Note: This test can be quite slow when running in CPU mode, so keep the threadCount low unless your on GPU // Also note that by default Darwin can't sustain > ~128 connections without adjusting limits - threadCount := 32 - if maxQueue := envconfig.MaxQueue(); maxQueue != 0 { - threadCount = int(maxQueue) - } else { - t.Setenv("OLLAMA_MAX_QUEUE", strconv.Itoa(threadCount)) - } + threadCount := 16 + t.Setenv("OLLAMA_MAX_QUEUE", strconv.Itoa(threadCount)) req := api.GenerateRequest{ Model: "orca-mini",