Skip to content

Update latest-results with post-fix benchmark run#28

Closed
kinto0 wants to merge 1 commit into
microsoft:mainfrom
kinto0:fix/update-latest-results-only
Closed

Update latest-results with post-fix benchmark run#28
kinto0 wants to merge 1 commit into
microsoft:mainfrom
kinto0:fix/update-latest-results-only

Conversation

@kinto0

@kinto0 kinto0 commented Apr 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Re-ran full unfiltered bench-servers after the tsp_core config fix
  • Filtered runs (--server/--protocol) intentionally skip updating latest-results.md, so it still showed the pre-fix Pyrefly failure
  • Updated latest-results.md and per-server JSON/JSONL result files

Depends on: #24 (environments.py symlink fix) and #27 (tsp_core config fix) — merge those first

Test plan

  • Before: latest-results.md shows: Pyrefly | no | 221.27 | ... | 1 (tsp_core failed point)
  • After: latest-results.md shows: Pyrefly | yes | 316.80 | 0.17 | 8 | 40 | 100% | 0. All 4 servers benchmarked. Pyrefly: 0 failures across 8 suites. pylsp-mypy: 5 failures (pre-existing Jedi issues, unrelated).

Re-ran full unfiltered bench-servers after the tsp_core config fix.
Filtered runs (--server/--protocol) intentionally skip updating
latest-results.md, so it still showed the pre-fix failure.

Test plan:
  Before: latest-results.md shows:
    Pyrefly | no | 221.27 | ... | 1 (tsp_core failed point)
  After:  latest-results.md shows:
    Pyrefly | yes | 316.80 | 0.17 | 8 | 40 | 100% | 0
    All 4 servers benchmarked. Pyrefly: 0 failures across 8 suites.
    pylsp-mypy: 5 failures (pre-existing Jedi issues, unrelated).
@kinto0 kinto0 closed this Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant