Skip to content

Failure to save the cache should not fail the entire run #592

@thetorpedodog

Description

@thetorpedodog

Description:

When running a workflow, there may be an issue which causes the cache not to be saved. This should not cause the entire run to be reported as a failure.

Action version:

v4.5.0

Platform:

  • Ubuntu
  • macOS

Runner type:

  • Hosted

Tools version:

Independent of Python version.

Repro steps:

  1. Include a setup-python step in a workflow with caching enabled.
  2. Have it happen to run at a time when the cache servers are acting flaky.

Example failed run: https://github.com/single-cell-data/TileDB-SOMA/actions/runs/3960808578/attempts/1

Expected behavior:

If the run finishes successfully, but the cache cannot be uploaded to the cache server, the failure to create the cache entry should be ignored.

Actual behavior:

When the cache fails to upload, the run is failed despite completing successfully in all other respects.

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy