Skip to content

Inconsistent reaping. #212

Description

@dzink

On app2.

What I did:
I have three different pull requests A B C, totaling 9.03G out of my 10G limit. All were active and none should be significantly larger than another. One build on C is pinned. I pushed a new commit to A, then a new commit to B.

What I expected to happen:
For reaping purposes, I expected one of the older PR's on B to be reaped, since now that one would be stale.

What actually happened:
The newest build on A that I had just built was reaped, as was the previous build on A. None of the builds on B were reaped, so I ended up with a stale B build I didn't need instead of the fresh build on A I just pushed.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions