Skip to content

[WHM] Smoke Create Cross-Repo PR - Persistent Schedule Failures (Systemic Bug) #23447

Closed as not planned
Closed as not planned
[WHM] Smoke Create Cross-Repo PR - Persistent Schedule Failures (Systemic Bug)#23447
Labels
cookieIssue Monster Loves Cookies!

Description

@github-actions
github-actions
bot
opened on Mar 29, 2026

Workflow: Smoke Create Cross-Repo PR

Priority: P1 — Every scheduled run has been failing since at least 2026-03-25.

Status (Schedule Runs Only)

Run Date Conclusion
#434 (23698264903) 2026-03-29T01:05Z ❌ failure
#431 (23685784887) 2026-03-28T13:01Z ❌ failure
#428 (23673954896) 2026-03-28T01:04Z ❌ failure
#418 (23647492346) 2026-03-27T13:03Z ❌ failure
#417 (23625940156) 2026-03-27T01:04Z ❌ failure
#410 (23595764504) 2026-03-26T13:03Z ❌ failure
#403 (23572288331) 2026-03-26T01:04Z ❌ failure
#383 (23542417783) 2026-03-25T13:03Z ❌ failure

PR-triggered runs are skipped (this smoke test does not run on PR events).

Root Cause

Same systemic push_repo_memory → Post Setup Scripts bug as #23151:

##[error]Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under
'/home/runner/work/gh-aw/gh-aw/actions/setup'.
Did you forget to run actions/checkout before running your local action?
```

The `push_repo_memory` job checks out the `memory/*` branch, causing the `actions/setup` local action to disappear from the working tree. The Post Setup cleanup step then fails.

Additionally the `detection` job fails:
```
##[error]❌ Failed to parse detection result: No THREAT_DETECTION_RESULT found in detection log.

This secondary failure is a consequence of the agent job failing.

Impact

  • Smoke test for cross-repo PR creation is not running
  • Cannot detect regressions in cross-repo PR workflow functionality
  • Contributes to overall health score degradation

Fix Required

Fix the systemic push_repo_memory → Post Setup Scripts bug in compiler_yaml.go — add a git checkout main restore step after the memory push so that actions/setup is accessible for Post Setup cleanup. See #23151 for full analysis.

References

  • Detected by WHM run §23708489882
  • Related issue: #23151 (PR Triage Agent — same bug)
  • Related issue: #23193 (Smoke Update Cross-Repo PR — same bug)

Generated by Workflow Health Manager - Meta-Orchestrator

Generated by Workflow Health Manager - Meta-Orchestrator · ◷

  • expires on Mar 30, 2026, 12:04 PM UTC

Activity

  1. github-actions
    added
    cookieIssue Monster Loves Cookies!
    on Mar 29, 2026
  2. github-actions
    added a parent issue on Mar 29, 2026

  3. github-actions commented on Mar 29, 2026

    @github-actions
    github-actionsbot
    on Mar 29, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  4. github-actions commented on Mar 29, 2026

    @github-actions
    github-actionsbot
    on Mar 29, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  5. github-actions commented on Mar 29, 2026

    @github-actions
    github-actionsbot
    on Mar 29, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  6. github-actions commented on Mar 29, 2026

    @github-actions
    github-actionsbot
    on Mar 29, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  7. github-actions commented on Mar 29, 2026

    @github-actions
    github-actionsbot
    on Mar 29, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  8. github-actions commented on Mar 29, 2026

    @github-actions
    github-actionsbot
    on Mar 29, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  9. github-actions commented on Mar 29, 2026

    @github-actions
    github-actionsbot
    on Mar 29, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  10. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  11. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  12. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  13. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  14. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  15. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  16. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  17. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  18. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  19. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  20. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  21. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    Status Update — 2026-03-30T12:08Z

    Persistent schedule failures continue. This is the same systemic bug as Smoke Update Cross-Repo PR (#23193).

    Run Trigger Conclusion Date
    #442 schedule ❌ failure 2026-03-30T01:05Z
    #438 schedule ❌ failure 2026-03-29T13:01Z
    Earlier schedule runs schedule ❌ failure 2026-03-25+

    PR-triggered runs are skipped (correct — this workflow uses if: github.event_name == 'schedule').

    Every schedule run has been failing since at least #383 (2026-03-25). This is now 8+ consecutive schedule failures.

    Root cause: Same push_repo_memory git branch checkout issue. After push_repo_memory checks out the memory/* branch, actions/setup directory is gone from workspace, causing the workflow to fail in Post Setup Scripts.

    Effort estimate: Low — requires a one-line git checkout HEAD restore in the push_repo_memory job template in pkg/workflow/compiler_yaml.go.

    WHM run §23743866195 — 2026-03-30T12:08Z

    Note

    🔒 Integrity filter blocked 2 items

    The following items were blocked because they don't meet the GitHub integrity level.

    • #19099 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18407 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

    To allow these resources, lower min-integrity in your GitHub frontmatter:

    tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

    Generated by Workflow Health Manager - Meta-Orchestrator · ◷

  22. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  23. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    🍪 Issue Monster has assigned this to Copilot!

    I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

    The Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ◷

  24. github-actions commented on Mar 30, 2026

    @github-actions
    github-actionsbot
    on Mar 30, 2026 – with GitHub Actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-03-30T12:04:47.019Z.

    Closed by Workflow

  25. github-actions
    closed this as not plannedon Mar 30, 2026
  26. Copilot
    added a commit that references this issue on Mar 30, 2026

    fix: restore actions folder in safe_outputs job after cross-repo chec…

    7ddb9f1
  27. pelikhan
    added a commit that references this issue on Mar 30, 2026

    fix: restore actions/setup after cross-repo checkout in safe_outputs …

    8b7f3c4
  28. Copilot
    added a commit that references this issue on Mar 31, 2026

    fix: add restore actions folder step to agent job when external root …

    2d689c3
  29. pelikhan
    added a commit that references this issue on Mar 31, 2026

    fix: restore actions/setup after external root checkout in agent job (#…

    6e45e1e
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

    cookieIssue Monster Loves Cookies!

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions