test(install): make reprobe test guard the block-list skip regression#367
Conversation
The reprobe fixture used an entry with an empty block_kernel_drivers, so a `block_kernel_drivers.len != 0` skip in probeAndReprobeDrivers (which would strand the real Vader 5, block list ["xpad"]) left the test green. Pin the fixture's block list to mirror production so the test fails on that regression. Verified in the canonical Docker image: injecting the skip flips the test to fail; removing it passes.
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe reprobe driverless-interface test's ChangesReprobe Test Fixture Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Surfaced by an adversarial review of the #355 install-migration hardening (#365). The reprobe unit test was green-but-blind to the exact regression it should catch.
install: reprobe writes only driverless interfacesused a fixture entry with an emptyblock_kernel_drivers.block_kernel_drivers.len != 0skip inprobeAndReprobeDrivers(the guard explicitly rejected during fix(install): apply block_kernel_drivers changes to connected devices and across install modes #365 review, because it would strand the real Vader 5 whose block list is["xpad"]) would NOT skip an empty-block entry — so the test passed even with that regression present.["xpad"]so it mirrors production and fails on that skip.Test-only change; no production behavior change.
Test plan
Verified in the canonical Docker image (
zig 0.15.2):zig build test -Dtest-filter="install: reprobe"passes.if (entry.block_kernel_drivers.len != 0) continue;intoprobeAndReprobeDrivers→ the test fails at the1-1.4:1.1write assertion (falsifiability confirmed).zig build test-tsan -Dtest-filter="install: reprobe"passes.Summary by CodeRabbit