-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Tests - Use base image for frontend tests #190
Tests - Use base image for frontend tests #190
Conversation
/test presubmit-e2e-test |
How much time does this actually save? Looks to me like too many lines of code if they just save us a few seconds of test time. |
|
This is just basic prudence. Do not download/clone when you do not need to. Apart from big decrease in image build times, this reduces the failures due to temporary network problems and also saves us from completely broken check-in process. Here is how the complete test failure looks like:
So at this moment no code can be checked in due to failing test. |
/test presubmit-e2e-test |
Doing |
5929dea
to
0309015
Compare
a009496
to
8bf6df8
Compare
/lgtm |
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.
LGTM, just two minor comments. Approving in case you want to merge.
/approve
test/frontend-integration-test/selenium-standalone-chrome-gcloud-nodejs.Docker/Dockerfile
Outdated
Show resolved
Hide resolved
test/frontend-integration-test/selenium-standalone-chrome-gcloud-nodejs.Docker/Dockerfile
Outdated
Show resolved
Hide resolved
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yebrahim 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 |
@Ark-kun: 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. |
The ml-pipeline-staging bucker is inaccessible by the image-builder container.
For some reason the root, not the active user owns the data copied using COPY
Cleaning files before committing the layer. Installing pip using apt-get (it's no longer in python-setuptools)
5abe22c
to
84e6a89
Compare
/area front-end |
@Ark-kun what's your plan about this PR? |
As the Frontend area lead, you can decide whether to close it or merge. This change was designed to improve the build speed and stability. The build speed is now pretty good even without this PR. The stability aspect remains valid. |
/retest |
I think this makes code base cleaner in separating env setup with actual test steps. Also great work automating image building. Let's merge this as long as tests are still passing. |
- Add installation from PyPi to sdk/README.md - Modify setup.py to read long_description from sdk/README.md - Replace relative links with absolute links to kfp-tekton GitHub repo - Add make distribution target for upload to testpypi Resolves kubeflow#185
This change moves the unchanging parts of the image to a base image so that they're not rebuilt every time. This improves performance and reliability.
The
Dockerfile
is now justThis change is