Parent Log: http://ci.aztec-labs.com/6831883003656c64 Command: aff82278d9e14e25 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/f880f14c946fb8464186d4178c5d49e391041988 Env: REF_NAME=gh-readonly-queue/next/pr-14967-b608f9359219731d3c03407689a4fadaaa5a0d45 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Thu Jun 12 14:17:30 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14967_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 14:17:33 PASS src/public/avm/avm_execution_environment.test.ts 14:17:33 Execution Environment 14:17:33 ✓ New call should fork execution environment correctly (5 ms) 14:17:33 ✓ New static call should fork execution environment correctly (1 ms) 14:17:33 14:17:33 Test Suites: 1 passed, 1 total 14:17:33 Tests: 2 passed, 2 total 14:17:33 Snapshots: 0 total 14:17:33 Time: 1.603 s 14:17:33 Ran all test suites matching /simulator\/src\/public\/avm\/avm_execution_environment.test.ts/i. 14:17:33 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?