Parent Log: http://ci.aztec-labs.com/3e13a93e0258dba1 Command: 47858aa9bf665f8a yarn-project/scripts/run_test.sh stdlib/src/tx/content_commitment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1bb4f0588a9dc5b1df622753aab1d907b3f12c7a Env: REF_NAME=gh-readonly-queue/next/pr-15245-534f06e45f48274efd53a2204c90cb0b91a53efb CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 25 08:19:12 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15245_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_5351cab9309588b7_next 08:19:15 PASS src/tx/content_commitment.test.ts 08:19:15 Content Commitment 08:19:15 ✓ serializes to buffer and deserializes it back (4 ms) 08:19:15 ✓ serializes to field array and deserializes it back (1 ms) 08:19:15 ✓ number of fields matches constant (3 ms) 08:19:15 08:19:15 Test Suites: 1 passed, 1 total 08:19:15 Tests: 3 passed, 3 total 08:19:15 Snapshots: 0 total 08:19:15 Time: 1.647 s 08:19:15 Ran all test suites matching stdlib/src/tx/content_commitment.test.ts. 08:19:15 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?