ci(tooling-tests): run the selector check's step wrapper test (base red: unrun linux-guard test)

Merged
AZ
6d ago
+4-0

What

This fixes a base red, which is priority zero. The registry step of cmux-next guards / tooling-tests is red on feat-cmux-next and on every PR:

Python test execution registry validation failed:
  - tests/test_check_objc_selectors_step.py: linux-guard lane is not run by any workflow

#27406 registered tests/test_check_objc_selectors_step.py in the linux-guard lane, but no workflow runs it. This PR adds a step for it in cmux-next-guards.yml tooling-tests, next to the other feat-cmux-next tooling tests. It is stdlib Python plus /bin/bash; its no-argument path is pure Python, and its macOS-only code runs only under --probe.

Commands:

  • python3 scripts/ci/validate_test_execution_registry.py: exits 1 on the base tip, as above, and 0 on the head.
  • python3 tests/test_check_objc_selectors_step.py: 2 tests OK.

Earlier heads of this PR also fixed tests/test_app_crate_licenses.py, to match a gate that had added cmux-chats-mirror. The base has since reverted that change (#28790), so this PR now takes the base's version of the file, and its only change is the workflow step.

Observed / Not run

  • Ran: both commands above.
  • Not run: the job itself. CI runs it on this PR.

šŸ¤– Generated with Claude Code