-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Use python to define the E2E test workflow for kfctl. #4148
Conversation
1faeee6
to
bed4311
Compare
b1dcdb4
to
96825a4
Compare
So close. It looks like delete test-dir failed. No longs show up if we filter by pod label (probably because of the known stackdriver issue). The error is
|
Failed on build-deploy the error is
|
96825a4
to
2ed8bd0
Compare
Looks like both basic-auth and iap workflows ran and only the step test_dir delete failed. |
* We need to write an E2E test for kfctl upgrade (kubeflow/kfctl#35). Before we do that we want to remove ksonnet from our existing E2E test. The E2E test for upgrades will be very similar to the kfctl E2E test so it makes sense to convert that test to python before writing the upgrade test. * Related to kubeflow#3035 migrate e2e tests off ksonnet * Code to setup default profile should not return an error if the secret already exists. This prevents us from calling apply multiple times. * Related to kubeflow/issues/3810; kfctl apply fails if we rerun it * Fixing working directory of juptyer test. * Update prow_config.yaml to use the new py_funcs for the kfctl_e2e tests * Update kfctl_go_test.py to determine whether we are using basic_auth from the KFDef spec rather than the command line arguments.
b7c3aac
to
18aa073
Compare
/assign @gabrielwen @yanniszark @gabrielwen This is ready for review. The tests passed before I rebased. The current run was triggered by the rebase but I expect them to pass as well. |
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
"--project=kubeflow-ci", | ||
# TODO(jlewi): Do we need a GITHUB_TOKEN? I'm guessing that | ||
# was for ksonnet. | ||
# "--github_token=$(GITHUB_TOKEN)", |
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.
seems like we can remove this?
"testing.test_deploy", | ||
"--project=kubeflow-ci", | ||
# TODO(jlewi): Do we still need a GITHUB_TOKEN? | ||
# "--github_token=$(GITHUB_TOKEN)", |
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.
ditto.
* Once kfctl upgrade is ready we will have to update this test to actually run. * kubeflow#4148 needs to be submitted first. * We will also need to update the test after kubeflow#4187 is merged. That splits kfctl_go_test.py into separate build and deploy steps.
@yanniszark Did you want to take a look at this? |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jlewi 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 |
Looks like the workflow Failed. I'm not sure why we are even running that workflow got triggered. I suspect an issue with computing the modified files because of the clone depth. |
/test all |
|
* Use python to define the E2E test workflow for kfctl. * We need to write an E2E test for kfctl upgrade (kubeflow/kfctl#35). Before we do that we want to remove ksonnet from our existing E2E test. The E2E test for upgrades will be very similar to the kfctl E2E test so it makes sense to convert that test to python before writing the upgrade test. * Related to kubeflow#3035 migrate e2e tests off ksonnet * Code to setup default profile should not return an error if the secret already exists. This prevents us from calling apply multiple times. * Related to kubeflow/issues/3810; kfctl apply fails if we rerun it * Fixing working directory of juptyer test. * Update prow_config.yaml to use the new py_funcs for the kfctl_e2e tests * Update kfctl_go_test.py to determine whether we are using basic_auth from the KFDef spec rather than the command line arguments. * Address comments.
* We need to write an E2E test for kfctl upgrade (kubeflow/kfctl#35). * Once kfctl upgrade is ready we will have to update this test to actually run. * kubeflow#4148 needs to be submitted first. * We will also need to update the test after kubeflow#4187 is merged. That splits kfctl_go_test.py into separate build and deploy steps.
* Use python to define the E2E test workflow for kfctl. * We need to write an E2E test for kfctl upgrade (kubeflow/kfctl#35). Before we do that we want to remove ksonnet from our existing E2E test. The E2E test for upgrades will be very similar to the kfctl E2E test so it makes sense to convert that test to python before writing the upgrade test. * Related to kubeflow#3035 migrate e2e tests off ksonnet * Code to setup default profile should not return an error if the secret already exists. This prevents us from calling apply multiple times. * Related to kubeflow/issues/3810; kfctl apply fails if we rerun it * Fixing working directory of juptyer test. * Update prow_config.yaml to use the new py_funcs for the kfctl_e2e tests * Update kfctl_go_test.py to determine whether we are using basic_auth from the KFDef spec rather than the command line arguments. * Address comments.
* Use python to define the E2E test workflow for kfctl. * We need to write an E2E test for kfctl upgrade (kubeflow/kfctl#35). Before we do that we want to remove ksonnet from our existing E2E test. The E2E test for upgrades will be very similar to the kfctl E2E test so it makes sense to convert that test to python before writing the upgrade test. * Related to kubeflow#3035 migrate e2e tests off ksonnet * Code to setup default profile should not return an error if the secret already exists. This prevents us from calling apply multiple times. * Related to kubeflow/issues/3810; kfctl apply fails if we rerun it * Fixing working directory of juptyer test. * Update prow_config.yaml to use the new py_funcs for the kfctl_e2e tests * Update kfctl_go_test.py to determine whether we are using basic_auth from the KFDef spec rather than the command line arguments. * Address comments.
We need to write an E2E test for kfctl upgrade (E2E test for kfctl upgrade kfctl#35).
Before we do that we want to remove ksonnet from our existing E2E test.
The E2E test for upgrades will be very similar to the kfctl E2E test
so it makes sense to convert that test to python before writing
the upgrade test.
Related to Migrate E2E tests off ksonnet #3035 migrate e2e tests off ksonnet
This change is