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