Ubuntu ARM SPV non-exclusive peer disconnection test timeout
Summary
dash-spv has an intermittent CI failure in
tests_disconnect::test_sync_with_peer_disconnection_non_exclusive on the
Ubuntu ARM SPV job.
This was seen on PR #749, whose diff only touches key-wallet-ffi files, while
this failure is in dash-spv reconnect/discovery behavior.
Failing CI
Failure mode
The test timed out after forcing three peer disconnections:
thread 'tests_disconnect::test_sync_with_peer_disconnection_non_exclusive'
panicked at dash-spv/tests/dashd_sync/helpers.rs:283:17:
Timeout after 3 disconnections. Current progress: ...
headers: WaitingForConnections, tip_height: 16000, target_height: 40000
filter_headers: WaitForEvents, current_height: 8000, target_height: 40000
filters: WaitingForConnections, stored_height: 1999, target_height: 40000
blocks: WaitForEvents, last_processed: 1188, requested: 42, downloaded: 14
The same run passed the other SPV jobs (Ubuntu / spv, Windows / spv, and
macOS / spv). The base branch CI for v0.42-dev at
53130869e5b9343ae59016323e5e5269e717a8fd also passed Ubuntu ARM / spv
shortly afterwards in run 25589413352.
Why this appears flaky / pre-existing
PR #749 changes only:
key-wallet-ffi/FFI_API.md
key-wallet-ffi/src/transaction.rs
key-wallet-ffi/src/transaction_tests.rs
It does not touch dash-spv, peer discovery, reconnect handling, or the failing
test. The failure is a timeout/race-like stall in the non-exclusive reconnect
path after forced peer disconnects on Ubuntu ARM.
Reproduction
With dashd test data configured as in CI:
cargo test -p dash-spv --test dashd_sync \
tests_disconnect::test_sync_with_peer_disconnection_non_exclusive \
-- --exact --nocapture
CI sets these environment variables via contrib/setup-dashd.py / workflow
setup:
DASHD_PATH
DASHD_TEST_DATA
RUST_BACKTRACE=1
Ubuntu ARM SPV non-exclusive peer disconnection test timeout
Summary
dash-spvhas an intermittent CI failure intests_disconnect::test_sync_with_peer_disconnection_non_exclusiveon theUbuntu ARM SPV job.
This was seen on PR #749, whose diff only touches
key-wallet-ffifiles, whilethis failure is in
dash-spvreconnect/discovery behavior.Failing CI
Failure mode
The test timed out after forcing three peer disconnections:
The same run passed the other SPV jobs (
Ubuntu / spv,Windows / spv, andmacOS / spv). The base branch CI forv0.42-devat53130869e5b9343ae59016323e5e5269e717a8fdalso passedUbuntu ARM / spvshortly afterwards in run
25589413352.Why this appears flaky / pre-existing
PR #749 changes only:
key-wallet-ffi/FFI_API.mdkey-wallet-ffi/src/transaction.rskey-wallet-ffi/src/transaction_tests.rsIt does not touch
dash-spv, peer discovery, reconnect handling, or the failingtest. The failure is a timeout/race-like stall in the non-exclusive reconnect
path after forced peer disconnects on Ubuntu ARM.
Reproduction
With dashd test data configured as in CI:
cargo test -p dash-spv --test dashd_sync \ tests_disconnect::test_sync_with_peer_disconnection_non_exclusive \ -- --exact --nocaptureCI sets these environment variables via
contrib/setup-dashd.py/ workflowsetup:
DASHD_PATHDASHD_TEST_DATARUST_BACKTRACE=1