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