Parent Log: http://ci.aztec-labs.com/4c037ca6f40cb048 Command: 71ec8227227d28e6 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/a45107e7f95b675cb2768b6bcb06483b511141f4 Env: REF_NAME=gh-readonly-queue/next/pr-15018-2731d9a8aebf63d05db1a786296abdf897c49490 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Thu Jun 12 17:45:35 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15018_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:45:37 PASS src/public/avm/avm_execution_environment.test.ts 17:45:37 Execution Environment 17:45:37 ✓ New call should fork execution environment correctly (4 ms) 17:45:37 ✓ New static call should fork execution environment correctly (1 ms) 17:45:37 17:45:37 Test Suites: 1 passed, 1 total 17:45:37 Tests: 2 passed, 2 total 17:45:37 Snapshots: 0 total 17:45:37 Time: 1.914 s 17:45:37 Ran all test suites matching /simulator\/src\/public\/avm\/avm_execution_environment.test.ts/i. 17:45:37 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?