Repository navigation
docs(evals): LongMemEval 2026-10-22 results on the merged main, with the development and validation split - #1872
Merged
Merged
Conversation
Contributor
Quality GateResult: ✅ all floors passed
Config: .github/quality-gate.yml. Workflow: |
added 2 commits
October 22, 2026 14:53
…e run into its own change
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.
What
Publishes two full LongMemEval-S runs after the recall changes (#1869, #1870, #1871): the run made on the branch before merging, and the definitive run on the merged main (
6ece9b07). Results, summaries, the failure transcripts of the misses, the per-question development/validation split, and the harness as it was run. The README shows base, pre-merge and merged side by side.Numbers (merged main)
The root READMEs (en, pt) quote the validation figure.
Checks
Results packs swept for credentials, tokens, e-mail addresses and local paths (none; paths are
<scratch>and~). Figures in the README were read fromsummary.json/summary-validation.jsonand from per-question comparisons of the three result files.