Skip to main content
Challenge

Build a Server Firmware Regression Detector and Change Approval Pipeline

Analyze performance benchmark diffs and driver logs across server firmware canary releases. Hosted Claude evaluates throughput degradations to approve or reject fleet-wide firmware deployment.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Analyze performance benchmark diffs and driver logs across server firmware canary releases. Hosted Claude evaluates throughput degradations to approve or reject fleet-wide firmware deployment.

Firmware Systems Qualification Engineer

Ingest benchmark execution logs comparing baseline firmware against newly deployed canary firmware versions.

Extract compute throughput, kernel launch latency, and PCIe error counters from normalized test runs.

Submit regression comparison tables to hosted Claude to determine whether performance deviations breach sign-off thresholds.

Output a structured firmware qualification scorecard and automated change ticket disposition.

Web qualification dashboard displaying regression delta charts and change approval sign-off toggles.

Create synthetic JSON files logging canary benchmark metrics, firmware versions, PCIe transaction retries, and latency deltas. Starter examples below are synthetic. They are not downloaded records.

NVIDIA DCGM exporter Extracts hardware performance counters and PCIe error telemetry patterns as described in DCGM documentation.

langgraph, anthropic, pydantic, pandas. LangGraph manages stateful multi-step review gates for processing, evaluating, and human-signing firmware qualification records. Hosted Claude API for technical regression analysis and qualification report drafting.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Flags canary builds showing greater than 3% throughput degradation compared to baseline.

Identifies non-zero PCIe replay or error counters introduced during canary execution.

Generates clear qualification verdicts: APPROVED_FOR_ROLLOUT, REJECTED_REGRESSION, or MANUAL_REVIEW.

```json [ { "input": { "target_firmware": "v555.42.02", "baseline_firmware": "v550.54.14", "benchmark_metrics": { "baseline_throughput_tps": 1250, "canary_throughput_tps": 1245, "pcie_replay_errors": 0, "kernel_launch_latency_us": 12.1 } }, "expected_output": { "qualification_verdict": "APPROVED_FOR_ROLLOUT", "throughput_delta_pct": -0.4, "pcie_error_flag": false, "approval_memo": "Performance delta within 3% tolerance and zero PCIe bus errors." } }, { "input": { "target_firmware": "v555.50.01", "baseline_firmware": "v550.54.14", "benchmark_metrics": { "baseline_throughput_tps": 1250, "canary_throughput_tps": 1120, "pcie_replay_errors": 42, "kernel_launch_latency_us": 18.5 } }, "expected_output": { "qualification_verdict": "REJECTED_REGRESSION", "throughput_delta_pct": -10.4, "pcie_error_flag": true, "approval_memo": "Significant throughput degradation (-10.4%) and active PCIe replay errors detected." } } ] ```

Evaluation and review only. Does not flash firmware or modify production cluster nodes. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Evaluation and review only. Does not flash firmware or modify production cluster nodes. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Flags canary builds showing greater than 3% throughput degradation compared to baseline. Identifies non-zero PCIe replay or error counters introduced during canary execution. Generates clear qualification verdicts: APPROVED_FOR_ROLLOUT, REJECTED_REGRESSION, or MANUAL_REVIEW.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest benchmark execution logs comparing baseline firmware against newly deployed canary firmware versions. Extract compute throughput, kernel launch latency, and PCIe error counters from normalized test runs. Submit regression comparison tables to hosted Claude to determine whether performance deviations breach sign-off thresholds. Output a structured firmware qualification scorecard and automated change ticket disposition.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Flags canary builds showing greater than 3% throughput degradation compared to baseline. Identifies non-zero PCIe replay or error counters introduced during canary execution. Generates clear qualification verdicts: APPROVED_FOR_ROLLOUT, REJECTED_REGRESSION, or MANUAL_REVIEW.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Web qualification dashboard displaying regression delta charts and change approval sign-off toggles.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Evaluation and review only. Does not flash firmware or modify production cluster nodes.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest benchmark execution logs comparing baseline firmware against newly deployed canary firmware versions.

  • Extract compute throughput, kernel launch latency, and PCIe error counters from normalized test runs.

  • Submit regression comparison tables to hosted Claude to determine whether performance deviations breach sign-off thresholds.

  • Output a structured firmware qualification scorecard and automated change ticket disposition.

Resources and assets

Reference links and supporting material

Dataset notes

Create synthetic JSON files logging canary benchmark metrics, firmware versions, PCIe transaction retries, and latency deltas. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

LangGraph

Runtime for stateful agent workflows.

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest benchmark execution logs comparing baseline firmware against newly deployed canary firmware versions...
  • Flags canary builds showing greater than 3% throughput degradation compared to baseline. Identifies non-zer...
  • Web qualification dashboard displaying regression delta charts and change approval sign-off toggles.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 2 configured tools

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • LangGraph · Optional
Orchestration
  • LangGraph · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Server Firmware Regression Detector and Change Approval Pipeline