Skip to content

test(kgemma): re-enable the Gemma 4 E2B tool-call smoke test — passes under engine 0.53.0 - #399

Merged
michalharakal merged 2 commits into
developfrom
test/gemma4-toolcall-reenable
Sep 2, 2026
Merged

michalharakal merged 2 commits into
developfrom
test/gemma4-toolcall-reenable

Conversation

@michalharakal

Copy link
Copy Markdown
Contributor

Gemma4E2BToolCallSmokeTest was @Ignored: the real E2B checkpoint emitted coherent English on the calculator prompt but no <|tool_call> markup (suspected prefill/sampling divergence). Verified locally against the published SKaiNET 0.53.0 with gemma-4-E2B-it-Q4_K_M.gguf: the model now emits <|tool_call>call:calculator{expression:...} and every assertion in the test holds (83 s). Re-enabling it as the regression guard; it stays env-gated on GEMMA4_E2B_MODEL_PATH, so CI without the checkpoint skips as before.

Also verified in the same pass (no changes needed): FunctionGemmaOfficialGgufTest 3/3 (parsed get_weather call) and QwenToolCallSmokeTest 2/2 with Qwen3-1.7B-Q8 (well-formed <tool_call> calculator call).

michalharakal and others added 2 commits September 2, 2026 15:01
… under engine 0.53.0

The test was @ignore'd because the real E2B checkpoint emitted coherent
English on the calculator prompt but no <|tool_call> markup. Against the
0.53.0 engine (self-healing kernel dispatch, dense-FP32-from-any-storage,
decode-shaped FP32 kernels) the Q4_K_M checkpoint now emits
<|tool_call>call:calculator{expression:...} and every assertion holds in
~80 s. Still env-gated on GEMMA4_E2B_MODEL_PATH, so CI skips without the
checkpoint.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@michalharakal
michalharakal merged commit 4deb7d6 into develop Sep 2, 2026
2 checks passed
@michalharakal
michalharakal deleted the test/gemma4-toolcall-reenable branch September 2, 2026 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant