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