Parent Log: http://ci.aztec-labs.com/92c2dda0ace2278e Command: a5511b51e55ea9c0 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_context.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/6ee95286f8bcc5bb6dca43222459ac5bf43a8a75 Env: REF_NAME=gh-readonly-queue/next/pr-15156-9cbd161a1dfa928167c1f969200b95df55ed4c6b CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 09:43:52 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15156_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_72cc967de95e1968_next 09:43:55 PASS src/public/avm/avm_context.test.ts 09:43:55 Avm Context 09:43:55 ✓ New call should fork context correctly (242 ms) 09:43:55 ✓ New static call should fork context correctly (4 ms) 09:43:55 09:43:55 Test Suites: 1 passed, 1 total 09:43:55 Tests: 2 passed, 2 total 09:43:55 Snapshots: 0 total 09:43:55 Time: 2.466 s 09:43:55 Ran all test suites matching simulator/src/public/avm/avm_context.test.ts. 09:43:55 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?