Stabilize flaky e2e shard failures#580
Closed
cursor[bot] wants to merge 1 commit into
Closed
Conversation
Co-authored-by: Christopher Speller <crspeller@users.noreply.github.com>
🤖 LLM Evaluation ResultsOpenAI
❌ Failed EvaluationsShow 1 failuresOPENAI1. TestReactEval/[openai]_react_cat_message
Anthropic
❌ Failed EvaluationsShow 1 failuresANTHROPIC1. TestReactEval/[anthropic]_react_cat_message
This comment was automatically generated by the eval CI pipeline. |
Collaborator
|
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
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
3 participants
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
This PR fixes the two remaining CI shard failures from commit
f31c29a72fa33fd3862c1f6ed2ee82f27ded7f3bafter checking for existing open PRs.e2e-tool-config-real-apisis already covered by open draft PR Fix flaky tool-config real API auto-run test #576 and did not duplicate that work.e2e/tests/tool-config/mock-api/tool-call-policies.spec.tsso the manual-approval + auto-run assertion waits for the renderedRead Channeltool card instead of assuming the latest bot post is the follow-up tool call.should disable reasoning configurationspec to use that mode.QA / verification:
gh pr list/gh pr viewbefore proceeding.gh run view --job 69224831269 --log-failed --repo mattermost/mattermost-plugin-agentsgh run view --job 69224831156 --log-failed --repo mattermost/mattermost-plugin-agentsgh run view --job 69224831148 --log-failed --repo mattermost/mattermost-plugin-agentscd e2e && npx playwright test tests/tool-config/mock-api/tool-call-policies.spec.ts tests/system-console/bot-reasoning-config.spec.ts --project=chromium --listCould not find a working container runtime strategy), so runtime verification is deferred to CI.Ticket Link
None
Screenshots
None
Release Note