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