Not Going the Distance: Filtering Tests by Build Graph Distance
summary
Aurora adds a direct hash to each Bazel target and computes two distances: a graph target distance (number of dependency hops to a directly changed target) and a package distance (edges that cross package boundaries). CI uses those metrics to skip tests whose package distance exceeds a tunable threshold, avoiding running expensive GPU simulations and cloud Monte Carlo jobs for distant changes, cutting cost and flaky failures while keeping close-unit tests and sanitizer runs for nearby edits, and the implementation is being merged into bazel-diff.
AI-written summary · about
related talks
45mUsing AI, statistics, and set theory to know what to test
45mSelective Testing + Q&A
11mLightning Talk – Testing Bazel’s Remote Execution API
35mBisection: It's Not Just for Git
33mFewer, Smarter, Faster: Scaling Testing @Spotify
28mWhen Can You Skip a Test? Tracking Test Impact
43mAre Your Tests Slowing You Down?
06mLightning Talk – Test Result Caching at Dropbox