Skip to content

Improve rubustness to temporary networking issues etc #84

Description

@consideRatio

While this action quite seldom fails, it does fail intermittently sometimes - at least once in 100 in repo's I'm using it in. It would be good to make it more robust!

Intermittent errors observed

Setup k3s failed

> Setup k3s v1.26
  [INFO]  Finding release for channel v1.26
  [INFO]  Using v1.26 as release
  [INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.26/sha256sum-amd64.txt
  Error: Process completed with exit code 22.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions