Parent Log: http://ci.aztec-labs.com/7d50fe3fd123434b Command: 9e675ed54321cc5a yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/96a426245731b3f48fcb6dd5e2a683c858706602 Env: REF_NAME=gh-readonly-queue/next/pr-15083-5867520ed258adecfee692b3694d693b2c7964ca CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 21:54:00 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15083_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 21:54:03 PASS src/public/avm/avm_execution_environment.test.ts 21:54:03 Execution Environment 21:54:03 ✓ New call should fork execution environment correctly (5 ms) 21:54:03 ✓ New static call should fork execution environment correctly (1 ms) 21:54:03 21:54:03 Test Suites: 1 passed, 1 total 21:54:03 Tests: 2 passed, 2 total 21:54:03 Snapshots: 0 total 21:54:03 Time: 2.255 s 21:54:03 Ran all test suites matching simulator/src/public/avm/avm_execution_environment.test.ts. 21:54:03 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?