Move Windows sandbox tests into a dedicated integration binary (#51678)

## Why

Elevated Windows sandbox tests share machine-wide accounts. Running them in the sharded core suite can consume test deadlines while shards wait for the account lock.

## What changed

Move the Windows sandbox tests into the Windows-only `windows_sandbox` integration-test binary. Update the nextest account-sharing group to select the entire binary instead of individual test names, so tests queue before their timeouts start. Keep the existing guard for coordination with other test binaries.

GitOrigin-RevId: 613925c9398b5acc8440fa34c658680f31f65c8b
This commit is contained in:
jif
2026-10-07 12:47:04 +00:00
committed by copyberry
parent b17c74cfd5
commit d83bb540ec
3 changed files with 10 additions and 9 deletions
-2
View File
@@ -251,8 +251,6 @@ mod web_search;
mod web_search_system_proxy;
mod websocket_fallback;
mod window_headers;
#[cfg(target_os = "windows")]
mod windows_sandbox;
mod workspace_roots;
mod worktree_trust;
@@ -1,3 +1,12 @@
//! Exercises the Windows sandbox in a dedicated integration-test binary.
//!
//! Elevated cases share machine-wide accounts, so keep them out of the sharded
//! core suite: otherwise several shards spend their test deadlines waiting for
//! the account lock. The guard still coordinates with other test binaries.
#![cfg(target_os = "windows")]
#![allow(clippy::expect_used)]
use anyhow::Context;
use codex_config::types::ApprovalsReviewer;
use codex_core::TurnInputRequest;