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