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