Parent Log: http://ci.aztec-labs.com/40634769b4b9c052 Command: 0742425f32083b75 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/04abcb151443d51d2f1b002a2412a083a9384a51 Env: REF_NAME=gh-readonly-queue/next/pr-15077-263498dd65e8700218979d7a94dbfd25b2a8a8a8 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 17 20:52:13 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15077_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 20:52:17 PASS src/public/avm/avm_execution_environment.test.ts 20:52:17 Execution Environment 20:52:17 ✓ New call should fork execution environment correctly (6 ms) 20:52:17 ✓ New static call should fork execution environment correctly (1 ms) 20:52:17 20:52:17 Test Suites: 1 passed, 1 total 20:52:17 Tests: 2 passed, 2 total 20:52:17 Snapshots: 0 total 20:52:17 Time: 2.084 s 20:52:17 Ran all test suites matching simulator/src/public/avm/avm_execution_environment.test.ts. 20:52:17 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?