fix(dashboard): backfill PR #267 Qwen3.6 journey after merge#367
Merged
Conversation
PR #267 was rewritten but data.json kept the July 6 eval, so record_merge never advanced landed_qwen36. Backfill the XL bidir eval, restore baseline_tps, and use ctx_128_tps for Qwen3.6 journey steps.
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
1 participant
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
0267-ca7028c) intodata.jsonand add it tolanded_qwen36at 463.27 tok/s (128-context)qwen36.baseline_tpsto 427.54 so the headline reads 427.54 → 473.27 tok/srecord_merge()now usesctx_128_tpsfor Qwen3.6 journey steps (not strongest-context headline tps)Root cause
PR #267 was completely rewritten after an early July eval;
data.jsonkept the stale 278.76 tok/s row, sosync_merged_dashboardhad nothing valid to record when #267 merged.Test plan
python3 -m unittest test_pr_eval_bot -vfromeval/(17 tests pass)