Parent Log: http://ci.aztec-labs.com/4377c19df791fe00 Command: e1600b85b5ffbde9 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/420e0a54fb4bfe8b04d7dd479f59ed0fe3ad3b74 Env: REF_NAME=gh-readonly-queue/next/pr-14922-106f897363bb5aee27ddd091b5be9641b011c5bb CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Thu Jun 12 16:13:56 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14922_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 16:13:59 PASS src/public/avm/avm_execution_environment.test.ts 16:13:59 Execution Environment 16:13:59 ✓ New call should fork execution environment correctly (6 ms) 16:13:59 ✓ New static call should fork execution environment correctly (1 ms) 16:13:59 16:13:59 Test Suites: 1 passed, 1 total 16:13:59 Tests: 2 passed, 2 total 16:13:59 Snapshots: 0 total 16:13:59 Time: 1.796 s 16:13:59 Ran all test suites matching /simulator\/src\/public\/avm\/avm_execution_environment.test.ts/i. 16:13:59 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?