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