-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
hack in field selectors for 3.6 #16541
hack in field selectors for 3.6 #16541
Conversation
e7df127
to
d452cf2
Compare
looks good enough to me |
"damning with faint praise" comes to mind... :) |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, deads2k The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/retest |
@stevekuznetsov @bparees extended-builds failed, but this ended up in queue |
What do you mean? Do you have some logs? |
Oh |
Builds are not blocking |
@csrwng can you help me sort out whether this error is real? I wouldn't expect to have changed anything for a test that used to work in 3.6. |
@deads2k this looks like a CI problem. In 3.6 not passing an arg would result in an error, but in 3.7 it only results in a warning. Looks like the builder image being used to run the test is a 3.7 one and not 3.6 (maybe latest?). But anyway not a real failure. |
it was a docker change (how docker handled you not supplying an ARG that the dockerfile defined). It went from being an error to a warning. We fixed the test in 3.7 when it broke (I guess when we updated docker at some point). We'll just need to backport the same fix to the 3.6 branch: you should be able to just cherry pick this into your PR: |
Docker changed the error for a non-existent --build-arg to a warning and changed the text of the message slightly, breaking one of our tests. Docker change: moby/moby@f150f42 Fixes: openshift#16197
@deads2k: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@deads2k this one is actually a bug that we fixed post-3.6. But nothing related to this pull. |
@deads2k we'll let you slide on that failure. |
Automatic merge from submit-queue |
This doesn't make any of the structural fixes to make field selectors more consistent and reliable across APIs, but it should enable compatible field selection in the 3.6 groupified APIs.
@bparees @gabemontero per request