fix(runner): record wall-clock latency on error rows

An error row with zero latency reads as an instant rejection when it
can be three exhausted request timeouts. A 651-second thinking-model
generation looked instant in the 2026-08-30 run and misdirected the
diagnosis toward gateway rejection. The error path now records the
wall clock across all attempts.
This commit is contained in:
2026-08-30 16:19:21 +01:00
parent 7616f4bdee
commit 6ad9dfbe42
2 changed files with 7 additions and 2 deletions
+1 -1
View File
@@ -5,7 +5,7 @@ models:
- uni/qwen3.6-27b
- uni/btl-4
concurrency: 8 # default when omitted; matches internal/config's default
request_timeout: 300s # default when omitted
request_timeout: 900s # default when omitted
max_tokens_default: 12000 # default when omitted; a reasoning model can spend
# thousands of tokens on reasoning_content before
# writing an answer, so this must stay generous