Skip to content

bors is/went haywire #7293

Closed
Closed
@huonw

Description

@huonw

@thestinger and I were trying to get #7289 merged, but it bounced the first time so he rebased, and I re-reviewed; but bors didn't pick it up, so @thestinger closed the PR and reopened it as #7292 (with the same commit). This meant that bors picked up #7289 (the original and closed PR). Closing #7292 and reopening #7289 removed #7289 from the status page and added #7292, so @thestinger closed both, and moved the commit to #7274. Bors then merrily merged #7289 (it was closed) before the previous patch (#7210) had finished running, and then remerged #7210 so there were 3 separate auto builds happening concurrently (two of the same pull request).

bors-madness

(It seems there are several bors processes running, e.g. the multiple sets of comments on #7274.)

It got worse... 3 lots of the one pull request (#7274):

bors-madness-2

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