Skip to content

tests: use permission profiles in unix escalation checks#20360

Closed
bolinfest wants to merge 1 commit into
pr20359from
pr20360
Closed

tests: use permission profiles in unix escalation checks#20360
bolinfest wants to merge 1 commit into
pr20359from
pr20360

Conversation

@bolinfest

@bolinfest bolinfest commented Apr 30, 2026

Copy link
Copy Markdown
Collaborator

Why

Unix shell escalation tests were still using a SandboxPolicy helper just to construct PermissionProfile fixtures. The runtime code under test already works with permission profiles and filesystem policies, so this kept legacy terminology in tests that are otherwise part of the new permission flow.

What Changed

  • Removed the permission_profile_from_sandbox_policy(...) test helper.
  • Replaced read-only fixtures with PermissionProfile::read_only().
  • Replaced the workspace-write fixture with PermissionProfile::workspace_write().
  • Left the explicit filesystem-policy fixtures unchanged where the test is intentionally exercising split filesystem behavior.

Verification

  • cargo test -p codex-core intercepted_exec_policy
  • cargo test -p codex-core execve_permission_request_hook_short_circuits_prompt

Stack created with Sapling. Best reviewed with ReviewStack.

This was referenced Apr 30, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Closing this pull request because it has had no updates for more than 14 days. If you plan to continue working on it, feel free to reopen or open a new PR.

@github-actions github-actions Bot closed this May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant