cmux NEXT tests: neutral machine name in the hover card colour test (base red from #32688)
Merged
TE
3d ago+5+5+0123456789-6-6-0123456789
#32688 added one more line naming a personal machine in HoverCardMachineColorTests, so the fleet rule lint (tests/test_ci_fleet_rule_lints.py, test_big_red, in the cmux-next CI guard group) went red on base. This PR fixes that red.
- The test fixture now uses the neutral name
my-vm, as that file's allowlist entry asked. - The entry is removed, since nothing in the file matches the lint any more (the allowlist only shrinks).
- The pick
"My-VM"still matches, because picks are keyed by the trimmed, lowercased name.
Observed / Not run
python3 tests/test_ci_fleet_rule_lints.py:test_big_redfails at 901d7e6450f and passes at this head.test_pkillstill fails locally, oncmux-next-ios/verifyfiles this PR doesn't touch.- Not run here: the Swift suite. The change only swaps a string literal.
Changelog
none
🤖 Generated with Claude Code
Agent session: agent session
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes the big-red fleet rule lint failure on base by using the neutral name my-vm in HoverCardMachineColorTests, which #32688 had reintroduced. Also removes the now-unused allowlist entry for that file. The "My-VM" pick case still passes because picks are keyed by the trimmed, lowercased name.