Parent Log: http://ci.aztec-labs.com/6edadffa1e55a16f Command: 2f5a01bdc943190c yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_context.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/b4e88ec5c5067a9b12be306fb60258508bcfdcf8 Env: REF_NAME=gh-readonly-queue/next/pr-15196-812a53d5d7c2057744dbf808172864443b5de7af CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Thu Jun 26 14:24:17 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15196_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_72cc967de95e1968_next 14:24:21 PASS src/public/avm/avm_context.test.ts 14:24:21 Avm Context 14:24:21 ✓ New call should fork context correctly (227 ms) 14:24:21 ✓ New static call should fork context correctly (2 ms) 14:24:21 14:24:21 Test Suites: 1 passed, 1 total 14:24:21 Tests: 2 passed, 2 total 14:24:21 Snapshots: 0 total 14:24:21 Time: 2.204 s 14:24:21 Ran all test suites matching simulator/src/public/avm/avm_context.test.ts. 14:24:21 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?