-
Notifications
You must be signed in to change notification settings - Fork 20
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
Integration CLI tests #483
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: AshwinHIBM The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @AshwinHIBM. Thanks for your PR. I'm waiting for a ppc64le-cloud 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. |
/ok-to-test |
@Rajalakshmi-Girish ppc64le-cloud/docker-ce-build#225 merged. Can you PTAL at this PR? |
cluster: k8s-ppc64le-cluster | ||
labels: | ||
preset-build-docker: "true" | ||
cron: 0 14 * * * |
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.
The time set at cron clashes with the existing job periodic-integration-test-docker
's cron time.
Choose a time stamp at which no other job gets trigger.
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.
Adjusted periodic-integration-test-docker
to 14:30 master...AshwinHIBM:test-infra:integration-cli#diff-d529e4fce74de0ef2b5f5f6f4131d73c755e5895ad4749261c3a15a2bcc6e61dR171
requests: | ||
cpu: "4000m" | ||
limits: | ||
cpu: "4000m" |
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.
Hope you have test run this job in your development cluster and visualized the view of test results in junit tab?
- image: quay.io/powercloud/docker-ce-build@sha256:f93b6d36ad414d30f584c6555d8c2116de58bd56601da36f4e13d4b5b624114a | ||
resources: | ||
requests: | ||
cpu: "4000m" |
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.
Are you sure this job would also need 4000m cpu like other docker jobs?
As this one aims at testing CLI, I suppose a lesser resource should suffice. Can you analyse on how much is the cpu required by this job?(Compare resource usage with similar job run upstream on x86)
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.
The upstream job uses 4000m but my experiment showed I can safely run periodic-integration-cli-docker
with 2000 and periodic-integration-test-docker
with 4000.
master...AshwinHIBM:test-infra:integration-cli#diff-d529e4fce74de0ef2b5f5f6f4131d73c755e5895ad4749261c3a15a2bcc6e61dR147
master...AshwinHIBM:test-infra:integration-cli#diff-d529e4fce74de0ef2b5f5f6f4131d73c755e5895ad4749261c3a15a2bcc6e61dR147
acaeff3
to
f61554d
Compare
/hold |
Job to trigger scripts in ppc64le-cloud/docker-ce-build#225
These tests will run against https://github.com/docker/cli