Skip to content

Partitioned proof runners regularly receive shutdown or communication lost #143

@zjp-CN

Description

@zjp-CN

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

Image

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.

Image

https://github.com/os-checker/distributed-verification/actions/runs/19005282648/job/54277999987


I've comfirmed that the following factors have no help to avoid such shutdowns

  • shrinking harnesses from auto to non-auto
  • the order of verification
  • parallelism through -j, -j=3, or no -j

cc model-checking/verify-rust-std#512

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions