Parent Log: http://ci.aztec-labs.com/810a77e866dce8f5 Command: 411627cf9c043d00 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/721a41c449eb0c4538a26180f6061f326128cf78 Env: REF_NAME=gh-readonly-queue/next/pr-14963-60e60f99f2634ad75a76b6e103858ff9ccd041d5 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 18:41:52 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14963_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 18:41:56 PASS src/public/avm/avm_execution_environment.test.ts 18:41:56 Execution Environment 18:41:56 ✓ New call should fork execution environment correctly (5 ms) 18:41:56 ✓ New static call should fork execution environment correctly (1 ms) 18:41:56 18:41:56 Test Suites: 1 passed, 1 total 18:41:56 Tests: 2 passed, 2 total 18:41:56 Snapshots: 0 total 18:41:56 Time: 2.263 s 18:41:56 Ran all test suites matching simulator/src/public/avm/avm_execution_environment.test.ts. 18:41:56 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?