Parent Log: http://ci.aztec-labs.com/83b4d5049d814dc9 Command: 97e7ef9a556fd7e6 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/86553a66d6e2c437b435016db7bedec6bd794ed7 Env: REF_NAME=gh-readonly-queue/master/pr-14912-015cb0cadef6a41094c3649f32a735392e1b9693 CURRENT_VERSION=0.87.9 CI_FULL=1 Date: Wed Jun 18 15:19:02 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14912_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_master 15:19:04 PASS src/public/avm/avm_execution_environment.test.ts 15:19:04 Execution Environment 15:19:04 ✓ New call should fork execution environment correctly (7 ms) 15:19:04 ✓ New static call should fork execution environment correctly (1 ms) 15:19:04 15:19:04 Test Suites: 1 passed, 1 total 15:19:04 Tests: 2 passed, 2 total 15:19:04 Snapshots: 0 total 15:19:04 Time: 1.521 s 15:19:04 Ran all test suites matching /simulator\/src\/public\/avm\/avm_execution_environment.test.ts/i. 15:19:04 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?