From f894c3f687b3e036dec0071936292ffa1c38e711 Mon Sep 17 00:00:00 2001 From: Michael Bolin Date: Thu, 2 Apr 2026 12:34:42 -0700 Subject: [PATCH] fix: add more detail to test assertion (#16606) In https://github.com/openai/codex/pull/16528, I am trying to get tests running under Bazel on Windows, but currently I see: ``` thread 'suite::user_shell_cmd::user_shell_command_does_not_set_network_sandbox_env_var' (10220) panicked at core/tests\suite\user_shell_cmd.rs:358:5: assertion failed: `(left == right)` Diff < left / right > : <1 >0 ``` This PR updates the `assert_eq!()` to provide more information to help diagnose the failure. --- [//]: # (BEGIN SAPLING FOOTER) Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/openai/codex/pull/16606). * #16608 * __->__ #16606 --- codex-rs/core/tests/suite/user_shell_cmd.rs | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/codex-rs/core/tests/suite/user_shell_cmd.rs b/codex-rs/core/tests/suite/user_shell_cmd.rs index c0fe8b535..f6abb5d62 100644 --- a/codex-rs/core/tests/suite/user_shell_cmd.rs +++ b/codex-rs/core/tests/suite/user_shell_cmd.rs @@ -350,13 +350,22 @@ async fn user_shell_command_does_not_set_network_sandbox_env_var() -> anyhow::Re .submit(Op::RunUserShellCommand { command }) .await?; - let end_event = wait_for_event_match(&test.codex, |ev| match ev { + let ExecCommandEndEvent { + exit_code, + stdout, + stderr, + .. + } = wait_for_event_match(&test.codex, |ev| match ev { EventMsg::ExecCommandEnd(event) => Some(event.clone()), _ => None, }) .await; - assert_eq!(end_event.exit_code, 0); - assert_eq!(end_event.stdout.trim(), "not-set"); + + assert_eq!( + exit_code, 0, + "shell command should execute successfully. stdout=`{stdout}`, stderr=`{stderr}`", + ); + assert_eq!(stdout.trim(), "not-set"); Ok(()) }