chore(deps): bump github.com/mcpchecker/mcpchecker from 0.0.12 to 0.0.14 in /e2e-tests/tools#102
Open
dependabot[bot] wants to merge 4 commits intomainfrom
Conversation
Bumps [github.com/mcpchecker/mcpchecker](https://github.com/mcpchecker/mcpchecker) from 0.0.12 to 0.0.14. - [Release notes](https://github.com/mcpchecker/mcpchecker/releases) - [Changelog](https://github.com/mcpchecker/mcpchecker/blob/main/CHANGELOG.md) - [Commits](mcpchecker/mcpchecker@v0.0.12...v0.0.14) --- updated-dependencies: - dependency-name: github.com/mcpchecker/mcpchecker dependency-version: 0.0.14 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
E2E Test ResultsCommit: 0ade07f |
mcpchecker v0.0.14 requires tasks to use the v1alpha2 format for proper llmJudge step execution. The v1alpha1 format's verify step with contains was causing "cannot run llmJudge step before agent" errors due to the new validation in the agent output extraction. Changes: - Add apiVersion: mcpchecker/v1alpha2 to all task files - Migrate steps to spec with structured verify phase - Wrap contains verification in llmJudge step declaration Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
❌ 2 Tests Failed:
View the full list of 2 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
The node fixtures were using plural "nodes" field which doesn't match
the ExportNodeResponse protobuf definition that expects singular "node".
This was causing wiremock errors:
"Cannot find field: nodes in message v1.ExportNodeResponse"
For streaming gRPC responses, the fixture should be an array of response
messages, each matching the proto message structure.
Changes:
- affected_nodes.json: wrap nodes in array of {node: {...}} objects
- empty.json: return empty object instead of {nodes: []}
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Investigated E2E test failures after upgrading to mcpchecker v0.0.14. Found that some tests fail because the OpenAI mock agent makes tool calls but doesn't send a final AgentMessageChunk update, causing llmJudge to fail with "cannot run llmJudge step before agent". Created reproduction test that demonstrates the issue: - Agent makes tool call and gets result (ToolCall + ToolCallUpdate) - But no AgentMessageChunk is sent afterward - ExtractOutputSteps produces only "tool_call" type steps - FinalMessageFromSteps returns empty string - llmJudge validation fails on empty Agent.Output The root cause appears to be in llmagent/acp_agent.go where the OnStepFinish callback may not be called in all scenarios, or step.Response.Content.Text() returns empty after tool calls. This may be related to the fantasy library update (v0.16.0 → v0.17.1) in mcpchecker v0.0.13. Test added to mcpchecker's pkg/agent/extract_test.go at: /tmp/mcpchecker/pkg/agent/extract_test.go Run with: cd /tmp/mcpchecker && go test -v -run TestAgentWithOnlyToolCallsNoFinalMessage ./pkg/agent/ See docs/mcpchecker-v0.0.14-bug-analysis.md for full analysis. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Contributor
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.
Bumps github.com/mcpchecker/mcpchecker from 0.0.12 to 0.0.14.
Release notes
Sourced from github.com/mcpchecker/mcpchecker's releases.
Commits
66c7902fix(acp): correctly extract agent output (#268)a99d8dedocs(cli): add --mcp-config-file flag to check command reference (#266)435a100feat(llmagent): support using google as provider as well as gemini (#262)1671e85build(deps): bump charm.land/fantasy from 0.16.0 to 0.17.1 in the go-dependen...afa31ccbuild(deps): bump sigstore/cosign-installer from 4.1.0 to 4.1.1 in the github...2a5d41ffix(llmagent): mcp client does not panic on initialization race (#261)bf75d5fdocs: pull docs out of README into structured docs folder (#252)e915dbdfeat: add flag to override mcp config file in eval yaml (#260)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)