ci: workflows failing due to "Connection timed out" errors #129
Description
Describe the bug
CI workflows are randomly failing due to "Connection timed out" errors when downloading the bitcoind binary from "https://bitcoincore.org/bin".
error: failed to run custom build command for `bitcoind v0.30.0`
Caused by:
process didn't exit successfully: `/home/runner/work/bdk/bdk/target/debug/build/bitcoind-99a74cf3b9077890/build-script-build` (exit status: 101)
--- stdout
filename:bitcoin-22.0-x86_64-linux-gnu.tar.gz version:22.0 hash:59ebd25dd82a51638b7a6bb914586201e67db67b919b2a1ff08925a7936d1b16
url:https://bitcoincore.org/bin//bitcoin-core-22.0/bitcoin-22.0-x86_64-linux-gnu.tar.gz
--- stderr
thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bitcoind-0.30.0/build.rs:98:49:
called `Result::unwrap()` on an `Err` value: IoError(Os { code: 110, kind: TimedOut, message: "Connection timed out" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Process completed with exit code 101.
For example: https://github.com/bitcoindevkit/bdk/actions/runs/6459716661/job/17538503354?pr=1160
To Reproduce
Push a new PR for master or release/0.29 branch.
Expected behavior
There should be no random failures.
Build environment
- BDK tag/commit:
masterandrelease/0.29branches - OS+version: linux or macos, likely all other
- Rust/Cargo version: stable
- Rust/Cargo target: linux or macos, likely all others
Additional context
Metadata
Metadata
Assignees
Type
Projects
Status