Parent Log: http://ci.aztec-labs.com/a0a5ca8d8b3bb5c7 Command: f643ae060f517c84 yarn-project/scripts/run_test.sh cli/src/utils/commands.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/be78cf2e908c8f2f34676d72c74c8b92a3f591d1 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Fri Jun 20 22:59:28 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=release-please--branches--next_amd64 Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4667fce1f8117690_next 22:59:31 PASS src/utils/commands.test.ts 22:59:31 parseFieldFromHexString 22:59:31 ✓ parses the field 0 correctly (4 ms) 22:59:31 ✓ parses the field 0x0 correctly (2 ms) 22:59:31 ✓ parses the field 0x1 correctly 22:59:31 ✓ parses the field 0x00 correctly 22:59:31 ✓ parses the field fa correctly (1 ms) 22:59:31 ✓ parses the field 123 correctly (1 ms) 22:59:31 ✓ parses the field 0xff correctly 22:59:31 ✓ parses the field 0x0000000000000000000000000000000000000000000000000000000000000003 correctly 22:59:31 ✓ parses the field 0x00000000000000000000000000000000000000000000000000000000000000003 correctly (1 ms) 22:59:31 22:59:31 Test Suites: 1 passed, 1 total 22:59:31 Tests: 9 passed, 9 total 22:59:31 Snapshots: 0 total 22:59:31 Time: 1.471 s 22:59:31 Ran all test suites matching cli/src/utils/commands.test.ts. 22:59:31 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?