Parent Log: http://ci.aztec-labs.com/28bed7997e2f8311 Command: 9b472e0d399d3b16 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_context.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/2b9c409698cf0f475a7a9f5884117c8ad2a4f79a Env: REF_NAME=gh-readonly-queue/next/pr-14987-f880f14c946fb8464186d4178c5d49e391041988 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Thu Jun 12 14:45:12 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14987_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_72cc967de95e1968_next 14:45:14 PASS src/public/avm/avm_context.test.ts 14:45:14 Avm Context 14:45:14 New call should fork context correctly (172 ms) 14:45:14 New static call should fork context correctly (2 ms) 14:45:14 14:45:14 Test Suites: 1 passed, 1 total 14:45:14 Tests: 2 passed, 2 total 14:45:14 Snapshots: 0 total 14:45:14 Time: 1.58 s 14:45:14 Ran all test suites matching /simulator\/src\/public\/avm\/avm_context.test.ts/i. 14:45:14 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?