Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

Merge bot re-runs all tests, doesn't detect fresh ones. #1043

Closed
brendandburns opened this issue May 23, 2016 · 3 comments
Closed

Merge bot re-runs all tests, doesn't detect fresh ones. #1043

brendandburns opened this issue May 23, 2016 · 3 comments
Labels
area/mungegithub lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@brendandburns
Copy link
Contributor

On the following PR:

kubernetes/kubernetes#25374

MergeBot said that tests were too old and re-ran. While it looks like unit tests were too old, there were fresh e2e test results that had only been run 2 hours previously.

MergeBot should only re-run tests that are actually stale using specific commands (e.g. unit test this) instead of re-running all tests.
@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 15, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 14, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/mungegithub lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brendandburns @k8s-ci-robot @fejta-bot