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