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