Parent Log: http://ci.aztec-labs.com/6cf94dee64914b13 Command: 557c108a8ed544a3: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/ed4f6d71e2ea98f43186114eb914d54b87dd1183 Env: REF_NAME=gh-readonly-queue/next/pr-15116-433ba6218aed45169029991a493e4232b30b8ec6 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 17 19:34:25 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15116_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_59222e5abc39f27e_next 19:34:25 +++ id -u 19:34:25 +++ id -g 19:34:25 ++ docker run -d --name p2p_src_msg_validators_tx_validator_double_spend_validator.test.ts --net=none --cpuset-cpus=0-127 --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'\''' 19:34:25 + cid=48cebce63ddb8ec705fa3ad30516a8749ea3932283e54863d78a9d4bebbde89e 19:34:25 + set +x 19:34:29 PASS src/msg_validators/tx_validator/double_spend_validator.test.ts 19:34:29 DoubleSpendTxValidator 19:34:29 rejects duplicates in non revertible data (457 ms) 19:34:29 rejects duplicates in revertible data (42 ms) 19:34:29 rejects duplicates against history (51 ms) 19:34:29 accepts txs with no duplicates (3 ms) 19:34:29 19:34:29 Test Suites: 1 passed, 1 total 19:34:29 Tests: 4 passed, 4 total 19:34:29 Snapshots: 0 total 19:34:29 Time: 2.381 s 19:34:29 Ran all test suites matching p2p/src/msg_validators/tx_validator/double_spend_validator.test.ts. 19:34:29 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?