Benchmark run
Started May 10, 2026, 8:42 PM · Recorded May 10, 2026, 9:12 PM · Ended May 10, 2026, 9:12 PM
Test suite v2 — Resilience · 045d4510abd0…
Generated May 10, 2026, 9:12 PM · qwen/qwen3-235b-a22b-2507
z-ai/glm-5.1459coding, cost, debugging, hallucination, reasoning, refactoring, security, speed, ui)--limit), not fail-fast (fail_fast=false)235/459 (51.2%)2261.71 / 3137 (72.1%)$1.0290.315s3.375s2.004s163.73 tok/s53/60 passed (88.3%), 93.9% score — fastest output (172.81 tok/s)28/30 passed (93.3%), 88.7% score — high accuracy in cost-aware tasks49/60 passed (81.7%), 92.0% score — strong on algorithmic tasks
easy (100% score) and hard (89.2%)3/9, 33.3%), $0.267 cost dominates total spend11/60 passed (18.3%), 60.4% score — weakest category11/60 passed (18.3%), 64.3% score — struggles with code transformation28/60 passed (46.7%), 73.3% score — frequent factual errors33/60 passed (55.0%), 75.8% score — inconsistent on concurrency and race conditionsui category cost $0.267 (26% of total) despite only 9 tests — due to high token output (e.g., ui::hard tests generated up to 14.9k tokens)reason-constraint-consistency-latency took 6.69sdebugging tests exceeded 3.5s (e.g., debug-deep-clone-v2: 3.88s)reasoning and refactoring show sharp drop in medium/hard levelsdebugging::hard pass rate: 55%, with failures in microtask-race, distributed-lock-expiryhalluc-api-array-flat, halluc-api-generator-return)regex-backtrack, integer-overflow, nan-equalitydebug-prototype-pollution-check-v2debug-prototype-pollution-merge-v2Spread syntax requires ...iterable[Symbol.iterator] to be a functionThe z-ai/glm-5.1 model performs well in coding, cost, and speed tasks, but struggles significantly with reasoning, refactoring, and hallucination avoidance. It shows strong output speed and low TTFT, but incurs high cost in ui tasks due to verbose generations. Critical weaknesses in debugging concurrency issues and reasoning under constraints suggest limitations in deep program understanding.
Per-model aggregates from overall_ranking.json for this run id.
Values are read from report.json when the benchmark wrote them.
Test suite
v2 — Resilience
Discovery
Full suite discovery (no --limit)
blxbench argv
tui
App version
v1.3.2
Resumed run
No
Score % vs mean latency where samples exist. Built from per-test rows in report.json when available.
Avg score % (bars) and strict success rate % (line) per cost cluster.
Per-test latency (seconds), successful timings only.
Normalized TTFT (inverted) vs decode tok/s per category for this run.
Average score % per metric dimension across all v2 tasks in this run.
Tests per scope (blue bars), estimated spend per scope (green bars), and mean $ ÷ merged rows per category (cyan line).
Per-test rows from report.json → results — by category (collapsed by default), then by difficulty. COMPL from details when present. The Visual column is omitted when no test in this run has a details.visual score. Judge: verdict and overall (0–100) from judge_validation / validation_model for coding/UI (hover for summary and subscores). No HTML or screenshots in this table. Cost: per-task USD from cost_usd or usage.cost when recorded. Suite: same manifest version/hash for every row (this run).
459 tasks in 9 categories · Grouped by category, then by difficulty; row order within each table matchesreport.json results (benchmark execution order)