bitcoin: ci: ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it
Usually they come with a follow-up error of Unable to connect to bitcoind after 2400s (or similar).
This is a tracking issue, because all tests are affected.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 24 (24 by maintainers)
Commits related to this issue
- test: Verify that ports won't collide Add check to verify that we don't have too many tests, which with the current implementation of p2p_port() would mean the first tests in the list would risk gett... — committed to hodlinator/bitcoin by hodlinator 2 years ago
- Merge bitcoin/bitcoin#31124: util: Remove RandAddSeedPerfmon 9bb92c0e7ffe2426b4afb80ddd4b4c96968316b5 util: Remove RandAddSeedPerfmon (Hodlinator) Pull request description: `RegQueryValueExA(HKEY... — committed to achow101/bitcoin by achow101 2 years ago
- Merge bitcoin/bitcoin#30660: qa: Verify clean shutdown on startup failure 10845cd7cc89fc83b4ee844dc577b391720bba9c qa: Add feature_framework_startup_failures.py (Hodlinator) 28e282ef9ae94ede4aace6b97... — committed to bitcoin/bitcoin by ryanofsky 2 years ago
Thanks for the added context @hebasto! ~There seems to be some agreement that upgrading to Python 3.12 would fix the issue. However, I was unable to find a documented fix, do you have a link? Your comment links to an issue with
subprocess.runbut it’s a higher-level function implemented on top ofsubprocess.Popenwhich we use.~Little experience with GHA, but yeah, those kind of things slowing down CI is not unheard of.
Thanks for pointing that out!
…that should indeed circumvent possible port-reuse issues stemming from OS PID reuse choices.
Given…
…we should be able to have 415 tests (4987 / 12) before tests at the beginning of the
test_listrisk colliding ports with tests at the end. From what I can see in test/functional/test_runner.py we have ~300 tests. 👍Also https://github.com/bitcoin/bitcoin/pull/28509.
Regarding process start issues, would there be any support for me attempting to integrate Microsoft SysInternals ProcDump into CI & test framework to be able to call
procdump -mm <PID>on thebitcoind.exeprocess and hopefully figure out where the process is stalling?This was just a wrong comment by myself. See https://github.com/bitcoin/bitcoin/pull/28509#issuecomment-1727885738
For reference: You can use
git log -S "unique_code_blob"to see when (and hopefully why) a piece of code was added. In this case it would be something like: