-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Add Kubernetes API coverage test consuming traces #20181
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
Hi @AwesomePatrol. Thanks for your PR. I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
270aa53
to
b8356e4
Compare
b8356e4
to
4cd188f
Compare
4cd188f
to
8b7e4c0
Compare
8b7e4c0
to
d4a9898
Compare
tests/robustness/coverage/README.md
Outdated
``` | ||
|
||
2\. Build and run Conformance tests from Kubernetes repository (this usually | ||
takes 30-40m or will time out after 1 hour). It needs to be run from Kubernetes git repository: |
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.
We should add note that Conformance tests
could be replaced with user prefered way to exercise K8s API. Conformance tests were just selected because ... (provide reasons).
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.
Updated to state that the goal is exercising Kubernetes API surface. Conformance tests are used, because they are a good starting point to achieve this, so I marked them as an example
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.
What I'm saying we should document that. In the step.
c08bde1
to
edc8fa9
Compare
It pulls a file from testdata with traces collected by Jaeger and then iterates over them in order to group them by Etcd gRPC method used. Signed-off-by: Aleksander Mistewicz <amistewicz@google.com>
All tools needed to process traces are already available in etcd/tests. Signed-off-by: Aleksander Mistewicz <amistewicz@google.com>
It makes it easier to know what methods were used from the tests outputs. Signed-off-by: Aleksander Mistewicz <amistewicz@google.com>
9554f9c
to
7daf63f
Compare
Signed-off-by: Aleksander Mistewicz <amistewicz@google.com>
7daf63f
to
587388f
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AwesomePatrol, serathius 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 |
It pulls a file from testdata with traces collected by Jaeger and then iterates over them in order to group them into those which use the contract interface, are known (and usually valid) uses outside of it. Later it can further analyze the parameters used over the run of Kubernetes conformance tests.