BLXBenchBLXBench UI
blxbench

Benchmark

Levels

Misc

DocsDownload blxbenchOur TestsPassSponsor / Partnership
DocsDownload blxbenchOur TestsPassSponsor / Partnership
BLXBenchBLXBench UI
blxbench

Benchmark

Levels

Misc

DocsDownload blxbenchOur TestsPassSponsor / Partnership
DocsDownload blxbenchOur TestsPassSponsor / Partnership
  1. Home
  2. Our Tests
  3. Summary Release Safety
blxbench

Test fixture

Summary Release Safety

Speedmediumscorer: contains_all

Latency-sensitive tasks where concise correct output matters.

How it is scored

The model receives the prompt (and optional system message). The run uses scorer contains_all with the JSON configuration below. Pass/fail and partial credit are determined entirely by that scorer against the model output; no human grading.

User prompt
Summarize in exactly 3 short bullet points:
To reduce deployment risk, the team introduced canary releases with automatic rollback, required feature flags for high-impact changes, and monitored golden signals for 30 minutes after each rollout. They also blocked releases when error budgets were exhausted.
Scorer config
{
  "expected_contains": [
    "canary",
    "rollback",
    "feature flags"
  ]
}
Run parameters

temperature

0

max_tokens

110

timeout (s)

120

type

scored

file

speed_medium_03.json

← PreviousSummary Data Quality
|
Next →Summary Customer Support

BLXBench

Community driven leaderboardPublic benchmark runner — run in your environment, share results with the community.

© 2026 BLXBench by bitslix.com

ProvenanceAggregated from user runs
Scope3 / 7 / 372
Latestrun_5434c2 / 7 / $0.00
TermsPrivacy