Evaluation Run Detail Report
Run ID: evalrun-b92aea0782574c129e3a933d662adcdd
Suite: core-daily-demo @ e3571509e8ac

Case Details

Baseline Summary: source=repo baseline=baseline-evalrun-3e8725979333434fa751c2dfb9a6b21f path=/evaluation/regression/baselines/core-daily-demo.yaml
Baseline Counts: status=skipped reason=resolved_model_mismatch
- component-restart-during-incident-window: verdict=fail failure=critical_evidence_missing subtype=- score=28 duration=11m30s workspace=ws-eval-1778572349654-4c7a65f6
  critical evidence: fail (Direct restart evidence is present within the incident window.; Direct panic evidence is present within the incident window.; Direct query interruption evidence is present within the incident window.)
- cpu-spike-during-incident-window: verdict=fail failure=critical_evidence_partial subtype=- score=30 duration=2m41s workspace=ws-eval-1778573040647-657eeeaf
  diagnosis penalties: reject_plan_cache_or_secondary_signals_as_primary_root_cause:-3
  critical evidence: partial (Evidence includes baseline-vs-incident capacity comparison context.)
  diagnosis: fail (Identifies a capacity or node-count shift as the primary driver of the CPU increase.; Avoids elevating plan cache hit=0 or similar secondary signals into the primary differentiating root cause.; Recommends capacity adjustment rather than plan cache tuning.)
- expensive-query-alert-correlation-during-incident-window: verdict=pass failure=- subtype=- score=70 duration=2m49s workspace=ws-eval-1778574447532-a3b1856e
  diagnosis penalties: reject_background_noise_as_primary_root_cause:-3
- expensive-query-spike-during-incident-window: verdict=pass failure=- subtype=- score=72 duration=6m03s workspace=ws-eval-1778574617141-618cf3a5
- panic-in-recoverable-goroutine: verdict=pass failure=- subtype=- score=70 duration=3m22s workspace=ws-eval-1778575526452-c5aeeaf3
  diagnosis penalties: reject_fake_alarm_or_unrelated_root_cause:-3
- service-degradation-during-incident-window: verdict=pass failure=- subtype=- score=75 duration=3m00s workspace=ws-eval-1778575345837-f2429901
- sql-tail-latency-spike-during-incident-window: verdict=fail failure=critical_evidence_partial subtype=- score=48 duration=6m05s workspace=ws-eval-1778574980199-cef3cb3e
  critical evidence: partial (Evidence correlates the abnormal heap path with an upstream issue or fixed release.)
  diagnosis: fail (Uses heap-profile stack evidence to localize the dominant problematic path.; Mentions the concrete GitHub issue id that matches the diagnosed path.; Recommends upgrading to a fixed version or build.)
- sustained-cpu-pressure-during-incident-window: verdict=fail failure=critical_evidence_partial subtype=- score=69 duration=7m12s workspace=ws-eval-1778573201918-68b5e3dc
  critical evidence: partial (Evidence shows allocation or GC pressure aligned with the CPU spike.; Optional heap profile evidence shows a hotspot aligned with the allocation-heavy path.)
- system-unavailability-during-incident-window: verdict=fail failure=critical_evidence_partial subtype=- score=54 duration=13m33s workspace=ws-eval-1778573634113-cff7d373
  critical evidence: partial (Evidence shows a major drop in available coprocessor worker capacity during the incident. [coprocessor-worker])
  diagnosis: fail (Identifies coprocessor worker capacity collapse rather than a pure query-side explanation.; Recommends capacity-protection actions such as minimum replicas or better scaling guardrails.; Recommends follow-up on the initial worker disappearance cause.)
- tail-latency-surge-during-incident-window: verdict=pass failure=- subtype=- score=100 duration=5m48s workspace=ws-eval-1778575728562-e2eaeeb7