Parent Log: http://ci.aztec-labs.com/e75f6976c94a80cc Command: 4f771e618b80a60c yarn-project/scripts/run_test.sh stdlib/src/logs/message_context.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/991b313d676f7cf820bb62a33e57cf5a4c8cf9cf Env: REF_NAME=gh-readonly-queue/next/pr-15075-af42fafbeb7d6a4440329d9e9e5b1df459fa2e2e CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 15:56:48 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15075_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_6ba914b2e0d9bad9_next 15:56:50 PASS src/logs/message_context.test.ts 15:56:50 MessageContext 15:56:50 serialization matches snapshots and output of Noir serialization (5 ms) 15:56:50 15:56:50 Test Suites: 1 passed, 1 total 15:56:50 Tests: 1 passed, 1 total 15:56:50 Snapshots: 1 passed, 1 total 15:56:50 Time: 0.611 s 15:56:50 Ran all test suites matching stdlib/src/logs/message_context.test.ts. 15:56:50 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?