CI: tor-connect and ldk-node check-api failing on all PRs #4587

CI: tor-connect and ldk-node check-api failing across PRs

Two CI jobs appear to be failing consistently across open PRs.

tor-connect

The job installs tor via apt, but doesn’t explicitly start the daemon before running tests. On recent ubuntu-latest runners, the service may not be ready when cargo test attempts to connect to 127.0.0.1:9050, leading to connection failures.

A possible fix would be to explicitly start the service (e.g. sudo systemctl start tor) and optionally wait for readiness before running tests.

LDK Node Integration Tests / check-api

This job runs on a self-hosted runner and has been failing consistently across PRs, including ones without relevant changes. This suggests a possible issue with the runner rather than the workflow itself.

Happy to put up a PR for the tor-connect fix if that sounds reasonable.