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