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