Skip to content

ci-demand: an unwritable cache is only a stderr warning and resume advice is wrong #120

Closed

Description

@scuttletoby

When the cache folder can't be written to, ci-demand only prints a warning on stderr. The --json output does not show it, and a stopped run still says "run again with the same --cache", which does not help because nothing was saved. On a big date range the run can then never finish.

Fix: report the unwritable cache in the JSON output, and do not suggest resuming when nothing was saved (or refuse to start a long run without a working cache). A failing test was written during the review.

From the quick-check review of #113: #113 (comment)

🤖 Generated with Claude Code

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    on Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions