Run details

aiWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix-1258-gemini-toolcall
- Runs and Agents
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

test(e2e): repair Gemini tool-schema wire assertions The converter now sends tool schemas via `parametersJsonSchema`, which aimock's Gemini handler never records (it copies only `parameters` into its `/v1/_requests` journal). Two consequences, both fixed here. `provider-tool-dispatch-wire` asserted the journal's `function.parameters`, so it failed deterministically after the switch. Drop that matcher and the comment describing the old SDK-side upper-casing; the surviving `name: 'google_search'` check is what the spec relies on to prove the tool was not swallowed into `{googleSearch: {...}}`. The new Gemini case in `arktype-tool-wire` asserted only `ok: true`, which the route returns unless the SDK throws. Had the raw mount stopped matching, the request would fall through to aimock's native Gemini handler, return 200, and the test would pass while proving nothing. Assert on the mount's `Schema accepted` reply instead, which it emits only after verifying the request carried `parametersJsonSchema` with `unit.const` and no `parameters`. Verified: pointing the route at a model the mount does not intercept fails on the new assertion while `ok: true` still comes back. Claude-Session: https://claude.ai/code/session_01PG6uRwgdsxF9vrj973KsKX

nx run-many --targets=build --exclude=examples/**,testing/**

Succeeded

4 CPU cores

read access token used

f1eb3ac11259

95%

Cache hits

60 of 63 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

63 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools