Skip to content
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

Fix test loophole for loading samples during KFP startup #1807

Merged
merged 1 commit into from
Aug 12, 2019

Conversation

IronPan
Copy link
Member

@IronPan IronPan commented Aug 11, 2019

For more context see
#1805 (comment)

We could remove this fix when ksonnet is deprecated.


This change is Reviewable

For more context see 
#1805 (comment)

We could remove this fix when ksonnet is deprecated.
@IronPan
Copy link
Member Author

IronPan commented Aug 11, 2019

/assign @numerology

@IronPan
Copy link
Member Author

IronPan commented Aug 11, 2019

/test kubeflow-pipeline-e2e-test

@IronPan
Copy link
Member Author

IronPan commented Aug 11, 2019

/test kubeflow-pipeline-sample-test

@numerology
Copy link

/test kubeflow-pipeline-e2e-test

1 similar comment
@IronPan
Copy link
Member Author

IronPan commented Aug 12, 2019

/test kubeflow-pipeline-e2e-test

@numerology
Copy link

/lgtm

@IronPan
Copy link
Member Author

IronPan commented Aug 12, 2019

/test kubeflow-pipeline-e2e-test

@@ -47,12 +47,18 @@ cd ${DIR}/${KFAPP}

## Update pipeline component image
pushd ks_app
# Delete pipeline component first before applying so we guarantee the pipeline component is new.
ks delete default -c pipeline
sleep 60s
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious why add the sleep here? Is the 'ks delete' nonblocking? If so, we might need to wait until the deletion completes here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes it's async delete. ks apply wont fail fast if it's applying to a terminating resource.
sleep 60s would ensure things are cleaned up.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the longer plan should be building the pipeline images before deploying the kubeflow and have the kubeflow deployment include the new images.
On the other hand, I thought the delete is a blocking call. If it is async, depending on a hardcoded timing is not good practice. If the deletion takes less than 60 seconds, we are wasting time in the tests; If the deletion takes more than 60 seconds, it is not working. Above all, I think we need a more deterministic way to wait for the pipeline deletion.
WDYT?

@IronPan
Copy link
Member Author

IronPan commented Aug 12, 2019

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: IronPan

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 1d8d451 into master Aug 12, 2019
@IronPan IronPan deleted the IronPan-patch-6 branch August 16, 2019 21:22
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this pull request Oct 22, 2023
* add wikimedia in the list of adopters

* add chrisalbon in wikimedia adopters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants