From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] support/testing: test_aichat: improve test reliability
Date: Thu, 19 Mar 2026 21:55:22 +0100 [thread overview]
Message-ID: <9c2d07bd0a2ebf510ae496045cc593c0@free.fr> (raw)
In-Reply-To: <20260318213805.640458-1-ju.o@free.fr>
On 18/03/2026 22:38, Julien Olivain via buildroot wrote:
> Since llama.cpp update in Buildroot commit [1], the test_aichat can
> fail for several reasons:
>
> The loop checking for the llama-server availability can fail if curl
> succeed, but the returned json data is not formatted as expected.
> This can happen if the server is ready but the model is not completely
> loaded. In that case, the server returns:
>
> {"error":{"message":"Loading
> model","type":"unavailable_error","code":503}}
>
> This commit ignore Python KeyError exceptions while doing the
> server test, to avoid failing if this message is received.
>
> Also, this new llama-server version introduced a prompt caching, which
> uses too much memory. This commit completely disable this prompt
> caching by adding "--cache-ram 0" in the llama-server options.
>
> [1]
> https://gitlab.com/buildroot.org/buildroot/-/commit/05c36d5d875713521f99b7bad48be316dcde2510
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
Applied to master.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-03-19 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 21:38 [Buildroot] [PATCH 1/1] support/testing: test_aichat: improve test reliability Julien Olivain via buildroot
2026-03-19 20:55 ` Julien Olivain via buildroot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c2d07bd0a2ebf510ae496045cc593c0@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox