Skip to content

[CI failure] CI scheduled runs #3353

Closed
Closed

Description

@github-actions

This issue tracks an unhealthy unattended CI workflow.
Subsequent failures are recorded in comments; a successful run in the
same trigger scope closes the issue automatically.

First unhealthy run

CI run #6987, attempt 1 concluded with cancelled.

  • Trigger: schedule
  • Branch: main
  • Commit: 32ba752
  • Completed: 2026-11-04T01:36:40Z

Created automatically by the CI workflow-health monitor.

Activity

  1. added
    bugSomething isn't working
    triageNeeds the team's attention
    CI/CDCI/CD infrastructure
    ci-workflow-healthAssigned to rolling issues managed by the ci-workflow-health.yml workflow.
    on Nov 4, 2026
  2. jpascucci-nv commented on Nov 4, 2026

    @jpascucci-nv
    Contributor

    These failures were from #3350
    The test was subsequently marked thread_unsafe so probably won't recur.

  3. github-actions commented on Nov 5, 2026

    @github-actions
    ContributorAuthor

    Recovered

    CI run #7025, attempt 1 concluded with success.

    • Trigger: schedule
    • Branch: main
    • Commit: f707a1f
    • Completed: 2026-11-05T01:25:20Z

    Closing this incident automatically.

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

    CI/CDCI/CD infrastructurebugSomething isn't workingci-workflow-healthAssigned to rolling issues managed by the ci-workflow-health.yml workflow.triageNeeds the team's attention

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions