Parent Log: http://ci.aztec-labs.com/424a32e00eb773f3 Command: 582720422b3f4dff yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_context.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/79e9bd1698f4bba6deade8f76c676f9bbb12ff74 Env: REF_NAME=gh-readonly-queue/staging/pr-15192-505a3c071181dbc5242dc8b655a9b2d69988c8db CURRENT_VERSION=1.0.0 CI_FULL=1 Date: Mon Jun 23 13:25:47 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15192_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_72cc967de95e1968_staging 13:25:50 PASS src/public/avm/avm_context.test.ts 13:25:50 Avm Context 13:25:50 New call should fork context correctly (206 ms) 13:25:50 New static call should fork context correctly (3 ms) 13:25:50 13:25:50 Test Suites: 1 passed, 1 total 13:25:50 Tests: 2 passed, 2 total 13:25:50 Snapshots: 0 total 13:25:50 Time: 2.418 s 13:25:50 Ran all test suites matching simulator/src/public/avm/avm_context.test.ts. 13:25:50 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?