Parent Log: http://ci.aztec-labs.com/994d9f116998c73d Command: 4aaecce8c7696119: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/3c9c3432af5707445b58094692f04efc45600b5f Env: REF_NAME=gh-readonly-queue/next/pr-15163-ffc8af0c47dad3be6fb4bfb9f3f5af6cd3a05a67 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Mon Jun 23 16:41:23 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15163_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_59222e5abc39f27e_next 16:41:23 +++ id -u 16:41:23 +++ id -g 16:41:23 ++ 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'\''' 16:41:23 + cid=db0df3fa925c4e3c485e97dc853b0eb7277f37351746a011a6640577cc96f19b 16:41:23 + set +x 16:41:25 PASS src/msg_validators/tx_validator/double_spend_validator.test.ts 16:41:25 DoubleSpendTxValidator 16:41:25 rejects duplicates in non revertible data (280 ms) 16:41:25 rejects duplicates in revertible data (32 ms) 16:41:25 rejects duplicates against history (14 ms) 16:41:25 accepts txs with no duplicates (2 ms) 16:41:25 16:41:25 Test Suites: 1 passed, 1 total 16:41:25 Tests: 4 passed, 4 total 16:41:25 Snapshots: 0 total 16:41:25 Time: 1.587 s 16:41:25 Ran all test suites matching p2p/src/msg_validators/tx_validator/double_spend_validator.test.ts. 16:41:25 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?