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