Trt 1716 omit apigroups 2 - #806
Draft
neisw wants to merge 2 commits into
Draft
Conversation
Contributor
|
Skipping CI for Draft Pull Request. |
Contributor
|
PR needs rebase. DetailsInstructions 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-sigs/prow repository. |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neisw The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We have the same test names both with and withou the
apigroup:Sippy shows non apigroup as active for this case. We will need to decide if we want to maintain the older hashes and default to them or update to the new stripped out hashes which should match the current versions.Or leave as is..
'''
{
"APIVersion": "v1",
"Kind": "TestOwnership",
"ID": "openshift-tests:77c80730450b104039f06cfc4d9e394e",
"Name": "[Conformance][sig-api-machinery][Feature:APIServer] local kubeconfig "lb-ext.kubeconfig" should be present on all masters and work [Suite:openshift/conformance/parallel/minimal]",
"Suite": "openshift-tests",
"Product": "OpenShift",
"Priority": 0,
"StaffApprovedObsolete": false,
"Component": "kube-apiserver",
"Capabilities": [
"APIServer"
],
"JIRAComponent": "kube-apiserver",
"JIRAComponentID": "14814"
},
{
"APIVersion": "v1",
"Kind": "TestOwnership",
"ID": "openshift-tests:77c80730450b104039f06cfc4d9e394e",
"Name": "[Conformance][sig-api-machinery][Feature:APIServer] local kubeconfig "lb-ext.kubeconfig" should be present on all masters and work [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel/minimal]",
"Suite": "openshift-tests",
"Product": "OpenShift",
"Priority": 0,
"StaffApprovedObsolete": false,
"Component": "kube-apiserver",
"Capabilities": [
"APIServer"
],
'''