Parent Log: http://ci.aztec-labs.com/501bee0986350724 Command: 02087f8fc23cff6c yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_context.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/78d87cb88633aee537d022d6fd8e57ceb74a3a95 Env: REF_NAME=gh-readonly-queue/next/pr-15024-78a5deb1c3aa24503935bbda20f9374ba35aa5c4 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 10:50:13 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15024_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_72cc967de95e1968_next 10:50:16 PASS src/public/avm/avm_context.test.ts 10:50:16 Avm Context 10:50:16 New call should fork context correctly (258 ms) 10:50:16 New static call should fork context correctly (4 ms) 10:50:16 10:50:16 Test Suites: 1 passed, 1 total 10:50:16 Tests: 2 passed, 2 total 10:50:16 Snapshots: 0 total 10:50:16 Time: 2.279 s 10:50:16 Ran all test suites matching simulator/src/public/avm/avm_context.test.ts. 10:50:16 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?