Parent Log: http://ci.aztec-labs.com/11d263800318d38c Command: 782f38c6306b3c5e:ISOLATE=1:NAME=p2p/src/msg_validators/tx_validator/double_spend_validator.test.ts yarn-project/scripts/run_test.sh p2p/src/msg_validators/tx_validator/double_spend_validator.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/d5a262aabc20f5384a720a0d831e2ec28badc7f9 Env: REF_NAME=gh-readonly-queue/next/pr-15042-17ea18ade041a1bb437806e047c30b29da124094 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Wed Jun 18 18:08:25 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15042_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_59222e5abc39f27e_next 18:08:26 +++ id -u 18:08:26 +++ id -g 18:08:26 ++ docker run -d --name p2p_src_msg_validators_tx_validator_double_spend_validator.test.ts --net=none --cpuset-cpus=0-63 --cpus=2 --memory=8g --user 1000:1000 -v/home/aztec-dev:/home/aztec-dev --mount type=tmpfs,target=/tmp,tmpfs-size=1g --workdir /home/aztec-dev/aztec-packages -e HOME -e VERBOSE -e GIT_CONFIG_GLOBAL=/home/aztec-dev/aztec-packages/build-images/src/home/.gitconfig -e FORCE_COLOR=true -e CPUS -e MEM aztecprotocol/build:3.0 /bin/bash -c 'timeout -v 600s bash -c '\''yarn-project/scripts/run_test.sh p2p/src/msg_validators/tx_validator/double_spend_validator.test.ts'\''' 18:08:26 + cid=46e3cb006ccbb73d88d9bac264424c59f0ef666f0664f53205df02ef61e94490 18:08:26 + set +x 18:08:28 PASS src/msg_validators/tx_validator/double_spend_validator.test.ts 18:08:28 DoubleSpendTxValidator 18:08:28 rejects duplicates in non revertible data (278 ms) 18:08:28 rejects duplicates in revertible data (35 ms) 18:08:28 rejects duplicates against history (36 ms) 18:08:28 accepts txs with no duplicates (2 ms) 18:08:28 18:08:28 Test Suites: 1 passed, 1 total 18:08:28 Tests: 4 passed, 4 total 18:08:28 Snapshots: 0 total 18:08:28 Time: 1.578 s 18:08:28 Ran all test suites matching p2p/src/msg_validators/tx_validator/double_spend_validator.test.ts. 18:08:28 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?