Parent Log: http://ci.aztec-labs.com/cd44163f3616f4c5 Command: b71f9d6a9e3f68ca yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/ee24aac96469b4f1cb8d70e614b2dd27bf0eb134 Env: REF_NAME=gh-readonly-queue/next/pr-15242-1c2c2ee2949dbe31742cc9501a31bf3bce8083cf CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 14:08:05 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15242_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 14:08:08 PASS src/public/avm/avm_execution_environment.test.ts 14:08:08 Execution Environment 14:08:08 ✓ New call should fork execution environment correctly (19 ms) 14:08:08 ✓ New static call should fork execution environment correctly (1 ms) 14:08:08 14:08:08 Test Suites: 1 passed, 1 total 14:08:08 Tests: 2 passed, 2 total 14:08:08 Snapshots: 0 total 14:08:08 Time: 1.762 s 14:08:08 Ran all test suites matching simulator/src/public/avm/avm_execution_environment.test.ts. 14:08:08 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?