Repository navigation
Conversation
a_hook_launch_does_not_advise_unenforced_placement read the host's real classifier tree. It accepted two host states (no tree; a tree it can place into, where it skipped) and failed on the third: a tree installed but the test running outside the delegated slice, which is any developer's shell on a host where `min finalize-install` has run. There the launch logs "this daemon cannot place a process in the classifier tree", a note the test did not accept. Both launches now answer over a root under the test's temp state dir, with an empty mount table, through the launcher's classifier_root and classifier_mountinfo seam the stand-in-tree tests already use. Every host reads as tree-less, so the test records one note, needs no skip, and the lint allow becomes an expect. Fixes gominimal/inbox#1215. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016CYvTxBZ7SjPrDqmzAv4No
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Approved: no findings at Nothing to do. Clobber: none seen. |
Fixes gominimal/inbox#1215.
Problem
a_hook_launch_does_not_advise_unenforced_placementread the host's real classifier tree at/sys/fs/cgroup/minimald.slice. It handled two host states:It failed on the third state: a tree is installed, but the test runs outside the delegated slice. That is any developer's shell on a host where
min finalize-installhas run. In that state the hook launch logs "this daemon cannot place a process in the classifier tree…", a note the test didn't accept.Change
Both launches now answer over a root under the test's temp state dir, with an empty mount table. They use the launcher's
classifier_root/classifier_mountinfoseam, which the stand-in-tree tests already use. As a result:#[allow(clippy::await_holding_lock)]becomes#[expect], since the test can no longer return before its first await.Test-only change; no production code is touched.
Verified
hook_launcher.for_hooks = false, the test fails with "a hook launch is not a session start and records no advisory". It still catches the regression it exists for.cargo nextest run -p minimal -p minimaldpasses 2359/2364. The 5 failures are the netns integration tests that need root, the same as on main on this host.-D warningsandcargo fmt --checkare clean.The issue also mentioned the guest refusal test's similar skip. It skips rather than fails on this host, so I left it alone here.
🤖 Generated with Claude Code
https://claude.ai/code/session_016CYvTxBZ7SjPrDqmzAv4No
Summary by CodeRabbit