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