Skip to content

P2 CI Metrics

Know which red builds are real.

Every failure on hardware gets sorted: a real firmware bug, a bench or harness problem, or a flake. CI Metrics reports it per product, so you fix the right thing and trust the passes.

app.stoutdata.ai/ci-metrics

CI Metrics

Merges exercised on real hardware, firmware bugs caught, and per-test flake rates for each product, reported by the connected CI pipeline.

to

Merges checked on hardware

67 / 69

97% of announced merges

Real FW bugs caught

3

2 bench or harness, 1 ambiguous

Flaky failures

16

Reds explained by a retry or same-commit rerun

Infra runs

5 / 259

Runs where the connectivity pre-check failed

Merges not checked on hardware

A merge counts as checked when this product's suite ran tests on that exact commit after passing the connection pre-check, or on a push that included it. In All products, a merge that touches shared code is counted once for each product it triggers. Two pull requests merged in separate pushes seconds apart can show the first as not checked even though its code ran in the second's run.

MergedProductRepoBranchCommit
Sep 20, 2026, 02:14 PMGatewayfleet/firmwaremaind4e0b71826
Sep 11, 2026, 04:52 PMSensor nodefleet/firmwarerelease/1.48f1a2c9ed0

Real FW bugs caught

Failures that were resolved by a newer commit, where the test harness blamed the device, the failing commit changed firmware, and the fix changed firmware and not the test harness.

First failedProductTestBoxBrokeFixed byHarness verdictStatusActions
2026-09-19Gatewaypower/brownout_recoverybench-02a3f81c2761 Debounce brown-out detector IRQ9d02e4f553 Widen the brown-out debounce windowDeviceAutomatic
2026-09-12Gatewayboot/banner_timeoutbench-0151b7aa00e5 Move the boot banner after clock init07adf1931b Print the banner before the PLL settlesDeviceAutomatic
2026-09-04Sensor noderadio/link_reconnectbench-047d3e5b8b89 Retune the PLL after each channel hop90c1f3ae9d Wait for PLL lock before the first hopDeviceAutomatic

Flakiest tests

ProductTestBoxesRunsAttemptsFailedPass on retryFlake rate
Gatewayboot/banner_timeout2586611816.7%
Gatewayio/gpio_loopback15861436.6%
Sensor noderadio/link_reconnect240445411.4%
Sensor nodesensor/imu_selftest14041214.9%
Stout v0.19.0What's newSupport
© 2026 Stout Data, Inc.

P2.1

Merges checked on hardware

For each product, see how many merged commits actually ran on a box, and a list of the ones that did not.

P2.2

Real firmware bugs, counted

A failure counts as a firmware bug when a newer commit fixed it, the harness blamed the device, the failing commit changed firmware, and the fix changed firmware and not the harness.

P2.3

Bench and harness problems, set aside

Failures that a bench or harness change resolved are listed separately with the reason, so they never inflate your bug count.

P2.4

Flaky tests, named

See the tests that pass on retry, with runs, attempts, failures, and a flake rate for each one.

P2.5

Infra runs, separated

Runs where the connectivity pre-check failed are counted on their own, so a bench that dropped off the network is not a test result.

P2.6

Your call, on the record

An admin can confirm or dismiss any row. The status column shows who decided, and Reset returns the row to the automatic label.

Related capability

03.3Workflows & CI

Next feature

P3PR Reviewers

See your own CI numbers.

Book a demo and we will connect a pipeline, run a few pull requests, and read the metrics together.