-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Fix test fail caused by #8606 #8782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for fixing this! @hklai @sebastienvas @rkpagadala could you guys figure out why bot is merging stuff that breaks |
/lgtm |
@PiotrSikora all required tests passed in #8606. I think prow always rebase before running tests. @sebastienvas can confirm and help figure out why. |
/test e2e-dashboard |
@hklai yeah, the tests passed on the change itself, but the merge commit was failing, since there were other changes merged in the meantime that needed updating in the PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hklai, JimmyCYJ, PiotrSikora The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I think #8606 gets merged by the bot without rebasing on the latest change on master. Some PR checked in after also needs to change but not included in #8606.