e2e-results: 2026-07-30 testbench run (claude harness) - #92
Merged
Conversation
12 runs (10 cases, 2 comparison cases x 2 server modes), graded: 11 passed, 1 needs_review (ro-absent-table, agent used Bash/ToolSearch despite the MCP-only prompt constraint). Tested against InfluxDB 3 Core 3.10.3 and InfluxDB 3 Enterprise 3.11.0-rc.1.
jstirnaman
temporarily deployed
to
cloud-serverless
July 30, 2026 05:02 — with
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the 2026-07-30 agent e2e testbench run for the runbook in #69's
AGENT_E2E_TESTS.md, executed via the docs-agent testbench harness (Claude only, per-case docker-compose live instances).Tested against InfluxDB 3 Core 3.10.3 and InfluxDB 3 Enterprise 3.11.0-rc.1.
Findings
expectedbehavior (correct tool choice, bounded queries, correct read/write behavior per server mode).ro-absent-table— the agent's answer content was correct (found: false, noquery_sqlrun), but the transcript shows it calledBash({"command":"true","description":"noop"}) andToolSearch, violating the case's explicit "Do not use shell commands" constraint. Left asneeds_reviewrather than a hard fail — the results schema has nofailedenum value (onlypassed/interrupted/needs_review).eff-broad-schema-cpu(default/operator mode) sent aquery_sqlcall with the query text underqueryinstead of the requiredqparam, gotMCP error -32603 (invalid_type, path: ["q"]), then retried correctly withq. Filed as query_sql: agent naturally sends 'query' param, tool requires 'q' — causes avoidable failed call #91 — the natural param name for a SQL-query tool isquery, notq, so this is likely to recur across agents/harnesses even though this run recovered.ro-wildcard-field-lowvs-high, reasoning low vs high): identical 4-call tool path and correctness, but high-effort reasoning cost 2959 vs 1895 tokens for no behavioral difference.eff-broad-schema-cpu, ro vs default): default mode usedget_measurementsinstead oflist_tables, and was both less efficient (12 vs 11 tool calls) and less reliable (1 failed call vs 0) for the same task.References
query_sqlcall, missingq)AGENT_E2E_TESTS.mdrunbook this run executes)docs-agent/testbench/README.md(harness design, grading process)Test plan
AGENT_E2E_RESULTSschema validation passed (node docs-agent/testbench/schemas/validate-e2e-results.mjsin docs-tooling, 12/12 runs valid) before this file was copied over