Compare · Codebase Pulse vs. Trunk & BuildPulse

A starved CI runner is not a flaky test. Stop quarantining healthy tests.

Point tools like Trunk Flaky Tests or BuildPulse ingest JUnit XML at the end of a pipeline and count pass/fail flips. They are blind to CPU saturation, disk stalls, and container crashes that happened on the runner while tests executed.

When a shared cloud runner hiccups or Redis dies mid-suite, XML-only tools flood dashboards with false flaky candidates. Codebase Pulse pairs TRX, nextest, and JUnit with 3-layer environment protection — and covers Build, Performance, and Codebase in the same workflow.

  • 3-layer false-flaky protection

    NoiseDetector (CPU, RAM, disk I/O, core count), IsMassFailure for suite-wide crashes, and selector drift detection keep outages off your flaky list.

  • Fix tests, do not only mute them

    See shared-fixture co-failures and parallel execution overlap hints — not just auto-quarantine by flip rate.

  • One agent for the whole pipeline

    One pulse-agent covers flaky tests, MSBuild/Cargo compile speed, benchmarks, load tests, and SARIF deltas — not a per-seat flaky-only SKU.

Feature comparison

Codebase Pulse vs. Trunk & BuildPulse

Side-by-side capabilities for .NET and Rust teams evaluating a pre-production CI signal layer.

CapabilityCodebase PulseTrunk & BuildPulse
Test report formatsVSTest .trx, cargo nextest / libtest JSON, JUnit XMLPrimarily JUnit XML
Runner hardware telemetryYes — excludes CPU saturation, RAM pressure, disk I/O stallsNo — VM starvation can look like flakiness
Mass infrastructure outage guardYes — skips flaky/baseline updates when shared deps crash the suiteNo — mass outages pollute flaky statistics
Partial test filter detectionDetects selector drift when a subset of tests ranLimited or manual
Root-cause diagnosticsCo-failure counts, parallel overlap, normalized signaturesFlip frequency and basic grouping
Automatic clean evictionEvicts resolved flaky/slow tests after consecutive clean runsOften manual status management
Broader CI observabilityBuild (.binlog/Cargo), Performance (BDN/k6/OTel), Codebase (SARIF/Git)Flaky tests only (or separate products)

On top of what you have

What Pulse adds if you already use Trunk & BuildPulse

Keep Trunk or BuildPulse for quarantine workflows if they work for you. Pulse adds runner context and pipeline breadth flaky-only tools skip.

  1. 01

    First-class VSTest TRX and cargo nextest — not JUnit XML alone for .NET and Rust suites.

  2. 02

    Hardware telemetry and mass-failure guards so Redis/DB outages do not become hundreds of false flaky candidates.

  3. 03

    Fixture co-failure and parallel overlap hints to fix races — not only flip-rate quarantine.

  4. 04

    Same PR comment as MSBuild/Cargo regressions, benchmarks, load tests, and SARIF deltas from one pulse-agent install.

Common questions

Evaluating Pulse alongside Trunk & BuildPulse

  • “Will Pulse auto-quarantine flaky tests like Trunk?”

    Pulse focuses on classification, PR headlines, and optional --guard — plus eviction when tests stay clean. Quarantine workflows remain in your CI policy; Pulse gives evidence (noisy run vs same-commit flip vs new failure).

  • “We already quarantine in Trunk — why add Pulse?”

    Quarantine hides symptoms. Pulse shows whether a flip was a noisy VM, a mass Redis outage, or a real same-commit race — and correlates it with compile and perf regressions on the same PR.