Parent Log: http://ci.aztec-labs.com/5acf0ac99541d93c Command: b3f72d9a489ed1c8 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/28bf32bfc2566751e8baa0a9125a9db20d474bee Env: REF_NAME=gh-readonly-queue/next/pr-15154-9071986bfe3af58c70d2c80c10f523e22bfe4cb4 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Fri Jun 20 15:28:22 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15154_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 15:28:24 PASS src/public/avm/avm_execution_environment.test.ts 15:28:24 Execution Environment 15:28:24 ✓ New call should fork execution environment correctly (5 ms) 15:28:24 ✓ New static call should fork execution environment correctly (2 ms) 15:28:24 15:28:24 Test Suites: 1 passed, 1 total 15:28:24 Tests: 2 passed, 2 total 15:28:24 Snapshots: 0 total 15:28:24 Time: 1.403 s 15:28:24 Ran all test suites matching simulator/src/public/avm/avm_execution_environment.test.ts. 15:28:24 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?