Parent Log: http://ci.aztec-labs.com/e954658c18809c99 Command: 68e9475192d7aeac yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/f495236d35f9bb0d1086b7ec79256c2c2b7c98b8 Env: REF_NAME=gh-readonly-queue/staging/pr-15201-f0619dd82429a5973f3e1da8d7eb0877264908e3 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Sat Jun 21 13:20:25 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15201_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_staging 13:20:28 PASS src/public/avm/avm_execution_environment.test.ts 13:20:28 Execution Environment 13:20:28 ✓ New call should fork execution environment correctly (6 ms) 13:20:28 ✓ New static call should fork execution environment correctly (1 ms) 13:20:28 13:20:28 Test Suites: 1 passed, 1 total 13:20:28 Tests: 2 passed, 2 total 13:20:28 Snapshots: 0 total 13:20:28 Time: 1.994 s 13:20:28 Ran all test suites matching simulator/src/public/avm/avm_execution_environment.test.ts. 13:20:28 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?