-
Notifications
You must be signed in to change notification settings - Fork 2.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
Tune etcd presubmit jobs #32731
Tune etcd presubmit jobs #32731
Conversation
/cc @jmhbnz |
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.
Thanks @ivanvc - Question around artifacts below. I'm still getting my head around how we are supposed to make artifacts work in prow.
@@ -168,6 +168,7 @@ presubmits: | |||
- | | |||
set -euo pipefail | |||
make gofail-enable | |||
export JUNIT_REPORT_DIR=${ARTIFACTS} |
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.
Curious on how this artifact dir is intended to work? Is there a bucket these artifacts will be stored in after the job has completed?
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.
They show up in the "Artifacts" tab of a build. For example, clicking "Artifacts" on build 1800476731895713792 takes you to the bucket. Inside there's an "artifacts" directory with the JUnit XML results.
I'm porting the following fragment, which seems to have been overlooked in the initial migration: https://github.com/etcd-io/etcd/blob/57907746e39da97ed3ce2fbd1f97e8ceb2ce8199/.github/workflows/tests-template.yaml#L69-L73.
However, I'm open to dropping saving the artifacts if we don't find value in storing them 🙂.
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.
Thanks for the explanation (and for updating it into etcd-io/etcd docs with screenshot) this is great functionality lets continue to save these.
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.
To be clear and 100% transparent, the screenshots you saw were from the Robustness tests. These are JUnit results 😄
Adjust memory and CPU requests accordingly to Grafana. Remove the optional argument after successful runs.
Adjust memory and CPU requests accordingly to Grafana. Remove the optional argumentafter successful runs.
f6061e1
to
cd68949
Compare
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.
Thanks @ivanvc
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ivanvc, jmhbnz 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 |
@ivanvc: Updated the
In response to this:
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. |
Tuning the integration and 386 unit test jobs after reviewing Grafana and Testgrid for the last two weeks.
Part of etcd-io/etcd#18065, kubernetes/k8s.io#6102.