Skip to content
This repository was archived by the owner on Jan 15, 2026. It is now read-only.
This repository was archived by the owner on Jan 15, 2026. It is now read-only.

bors sometimes makes PRs haunted #205

@Noratrieb

Description

@Noratrieb

it happened here rust-lang/rust#117494

  • a different PR, compiler: clippy::complexity fixes rust#121523, started being tested
  • CI failed
  • the tree was closed after a retry and then tried a few times
  • meanwhile, our friend 117494 was being try built
  • after the tree was reopened, somehow 117494 started being shown as currently testing
  • the try build completed
  • probably because the "Mark job as successful" job doesn't run in try, bors thought that it hasn't completed
  • Several hours later, it was still marked as testing, blocking the queue
  • I did bors retry, throwing it out and unblocking the queue
  • I closed the PR anyways because I was afraid bors would just push to master after the try build
  • I reopened the PR and tried again
  • it was now also makes as testing, not trying!
  • I closed the PR
  • PR's haunted

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions