Skip to content

fix active_pr continue respawn - #39

Open
junie-the-developer[bot] wants to merge 1 commit into
mainfrom
yana/fix-active-pr-continue-respawn
Open

fix active_pr continue respawn#39
junie-the-developer[bot] wants to merge 1 commit into
mainfrom
yana/fix-active-pr-continue-respawn

Conversation

@junie-the-developer

Copy link
Copy Markdown

What

Allow ready-lane same-task continuation to recover incomplete active_pr runs without creating a new task or duplicate pull request, while retaining the duplicate-work protection for successfully completed runs with a live PR.

Changes

  • Step 1 — Updated the respawn guard to allow continuation after incomplete recovery outcomes such as crashes, reclaim, orphan recovery, and timeouts.
  • Step 1 — Preserved blocking after completed work, with the existing deliberate-clear, never-run, and closed/merged-PR exceptions.
  • Step 1 — Added regression coverage for blocking, clear signals, recovery continuation, and re-arming after a later completed run.
  • Step 1 — Updated Kanban help and documentation to explain automatic continuation for incomplete recovery and the explicit unguard override after successful PR work.

…inue

Co-authored-by: Junie <junie@jetbrains.com>
@github-actions

github-actions Bot commented Aug 27, 2026

Copy link
Copy Markdown

૮ >ﻌ< ა ci review

ran on 3dd89bf — fix active_pr continue respawn [step 1] allow incomplete run

⚠️ Warnings

CI timings · View report · View job

Wall time 67m6s vs 7m8s (+840.7%). 18 job(s) slower, 3 faster, 4 unchanged.

  • Python tests / Run tests slice 4/12: +34.0s
  • Python tests / Run tests slice 11/12: +31.0s
  • Python tests / Run tests slice 12/12: -26.0s
  • Check contributors / check-attribution: +22.0s
  • Python tests / Run tests slice 3/12: +12.0s

OSV vulnerability scan · View job

5 known vulnerabilities found in pinned dependencies.

How to fix:

Review the findings in the Security tab. Update the affected dependencies if a patched version is available.

@junie-the-developer

Copy link
Copy Markdown
Author

CI triage follow-up on bot report #5443923472:

  • Python tests / Run tests slice 7/12 (original job 98638054908) classified as flake/transient, not caused by this PR diff.
  • Evidence: PR-touched kanban tests sit in slices 1/3/4 (all green); merge-base main 9a930535 was green including slice 7; same head SHA 3dd89bf reran green as job 98656338123, and All required checks pass job 98657037166 is green.
  • No product-code fix on fix active_pr continue respawn #39 (HARD: unrelated CI not greenwashed).
  • OSV lockfile CVEs left as unrelated/deps — not in scope for this PR.
  • Exact original pytest node ids were not recoverable (Azure blob logs blocked in sandbox); after rerun there are no remaining failing node ids.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants