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