Parent Log: http://ci.aztec-labs.com/30965617224928f2 Command: 1574a02ff8f30339 yarn-project/scripts/run_test.sh cli/src/utils/commands.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1677dac936d084443e64d6c4ba6e45d3958ba1f8 Env: REF_NAME=gh-readonly-queue/next/pr-15122-df0c3e8efd6211cf15eedf67d2a591cc54099ac8 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 18:31:02 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15122_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4667fce1f8117690_next 18:31:05 PASS src/utils/commands.test.ts 18:31:05 parseFieldFromHexString 18:31:05 parses the field 0 correctly (10 ms) 18:31:05 parses the field 0x0 correctly 18:31:05 parses the field 0x1 correctly 18:31:05 parses the field 0x00 correctly (1 ms) 18:31:05 parses the field fa correctly (1 ms) 18:31:05 parses the field 123 correctly 18:31:05 parses the field 0xff correctly 18:31:05 parses the field 0x0000000000000000000000000000000000000000000000000000000000000003 correctly 18:31:05 parses the field 0x00000000000000000000000000000000000000000000000000000000000000003 correctly (3 ms) 18:31:05 18:31:05 Test Suites: 1 passed, 1 total 18:31:05 Tests: 9 passed, 9 total 18:31:05 Snapshots: 0 total 18:31:05 Time: 1.914 s 18:31:05 Ran all test suites matching cli/src/utils/commands.test.ts. 18:31:05 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?