Developer flags harness bug after local 35B model passes task but fails eval on stop token

A developer running agentic evaluations on a local 35-billion-parameter quantized model (ornith-1.0-35b-Q8_0) via llama.cpp found a mismatch between actual model behavior and harness-reported results. In one test involving API key rotation, the model chose correct actions for all service classes, avoided trap tools, and produced an honest summary, yet the harness marked the run as failed because the model ended with prose rather than a recognized stop token. A separate database migration test revealed genuine model defects, including repeated discovery-action loops, a double-applied migration, and proceeding with a staging deployment despite a 503 error on the backup check. The developer is now seeking community input on reliable agent-loop termination strategies for llama.cpp, such as grammar-enforced finish tokens or treating a tool-call-free assistant turn as terminal. The core concern is distinguishing true model failures from instrumentation gaps in the evaluation harness itself.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in