Skip to content

Flaky in CI: 'restore failure cancels the run instead of resuming against the mutated presentation' #91

Description

@tnunamak

The reference-implementation suite failed this test on a docs-only PR (#90, deletion of markdown files plus one workflow trigger glob), then passed on rerun of the identical commit.

Evidence:

Second observed member of the flaky-in-hosted-CI class (a background-run projection test failed on docs-only PR #236 in June and passed locally 25/25).

Impact beyond noise: this repo currently has no required status checks, so red CI does not block merges; a flaky required check would be the worst of both worlds. Stabilizing this test is a prerequisite for making the full suite a required check.

Assisted-by: AI

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions