-
Notifications
You must be signed in to change notification settings - Fork 39.4k
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
New added CI tests can not start. #51681
Comments
/sig testing |
See also in #46079. @cblecker I see you triggered the two tests manually in some PRs, e.g. #50846 (comment). Any thoughts on this? |
Yeah, I triggered them because they didn't start on their own.. but it's good to raise this issue. I'm not sure who added those contexts, but they didn't start but were still marked as required by SQ. cc: @kubernetes/test-infra-maintainers |
Yes, today there is no way other than manually triggering newly added CI tests on pre-existing PRs. @soltysh this was what you also hit. |
Mind moving this isssue in the test-infra repository? |
@Kargakis |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
New added CI tests: pull-kubernetes-bazel-build and pull-kubernetes-bazel-test
can not start.
What you expected to happen:
those should start automatically.
How to reproduce it (as minimally and precisely as possible):
ref: #46341
it has ok-to-test label
but
The text was updated successfully, but these errors were encountered: