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