ci: linux64_multiprocess-test runner lost communication

[thepastaclaw]

CI runner lost communication in linux64 multiprocess test

Summary

The linux64_multiprocess-test / Test source GitHub Actions job can fail before
reporting a functional-test failure because the hosted runner loses
communication with GitHub.

Example:

• PR: fix: penalize oversized notfound messages #7348
• Run: https://github.com/dashpay/dash/actions/runs/27211941736
• Job: https://github.com/dashpay/dash/actions/runs/27211941736/job/80351321259
• Check run: linux64_multiprocess-test / Test source
• Result: failure

Observed failure

The check-run annotation is:

The hosted runner lost communication with the server. Anything in your workflow
that terminates the runner process, starves it for CPU/Memory, or blocks its
network access can cause this error.

No functional-test traceback was available from the GitHub log API for this job.
Requesting the job logs returned an Azure BlobNotFound response for the
redirected log blob.

Scope notes

The example PR only changes:

src/net_processing.cpp
test/functional/p2p_tx_download.py

The failing job did not report a failure in those files; the only surfaced
failure mode is the hosted-runner communication loss. This appears to be CI
infrastructure instability rather than a code/test regression in the PR.

Useful commands

gh api /repos/dashpay/dash/check-runs/80351321259/annotations
curl -L -H "Authorization: Bearer $(gh auth token)" \
  https://api.github.com/repos/dashpay/dash/actions/jobs/80351321259/logs