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 bunch of issues in prow test #866

Merged
merged 5 commits into from
Feb 27, 2019
Merged

Conversation

IronPan
Copy link
Member

@IronPan IronPan commented Feb 27, 2019

set -ex to avoid swallowing the errors silently

This change is Reviewable

@@ -29,6 +29,3 @@ remote_code_archive_uri="${code_archive_prefix}_${PULL_BASE_SHA}_${date_string}.

tar -czf "$local_code_archive_file" .
gsutil cp "$local_code_archive_file" "$remote_code_archive_uri"

Copy link
Contributor

Choose a reason for hiding this comment

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

Any reason why we move these two variables out of the test-prep script

Copy link
Member Author

Choose a reason for hiding this comment

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

i was having a hard time trace those environment variable as they are spread across multiple files. It's better to locate them in the same top level script.

Copy link
Contributor

@gaoning777 gaoning777 Feb 27, 2019

Choose a reason for hiding this comment

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

In fact, that is why I tried to move all shared env variable in the test_prep script, which also reduced code duplication.

Copy link
Member Author

Choose a reason for hiding this comment

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

Shouldn't the environment variable be determined by the caller? how is it different from other env variables in the top level script?

Copy link
Contributor

Choose a reason for hiding this comment

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

For env variables, yes. I mean, local variables such as PROJECT and GCR_IMAGE_BASE_DIR are not from the caller. TEST_CLUSTER_PREFIX and TEST_CLUSTER are also local variables that are used by these test scripts.

Above all, there are env variables that are from the caller and there are local variables that presubmit and postsubmit creates. My point was to move these shared local variables in the same script for better reference.

Copy link
Member Author

Choose a reason for hiding this comment

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

I moved them to deploy-kubeflow.sh since it's only used there.

The variable passing in these scripts start to become a bit casual. Given the complexity of the test script I think we might also consider switching to go/python based binary.

Copy link
Contributor

Choose a reason for hiding this comment

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

SG. Let's create an issue to keep track: #875

@IronPan
Copy link
Member Author

IronPan commented Feb 27, 2019

/test kubeflow-pipeline-e2e-test

1 similar comment
@IronPan
Copy link
Member Author

IronPan commented Feb 27, 2019

/test kubeflow-pipeline-e2e-test

@IronPan
Copy link
Member Author

IronPan commented Feb 27, 2019

fix #865

@IronPan IronPan changed the title [WIP] fix bunch of issues in prow test fix bunch of issues in prow test Feb 27, 2019
@IronPan
Copy link
Member Author

IronPan commented Feb 27, 2019

/assign @hongye-sun @gaoning777

@gaoning777
Copy link
Contributor

/test kubeflow-pipeline-e2e-test

@IronPan
Copy link
Member Author

IronPan commented Feb 27, 2019

The tests failed due to legit issue building e2e test image

�[39mbuild-basic-e2e-tests-image�[0m:	    creating build/temp.linux-x86_64-3.5/build/temp.linux-x86_64-3.5
�[39mbuild-basic-e2e-tests-image�[0m:	    x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fdebug-prefix-map=/build/python3.5-3.5.3=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.5m -c build/temp.linux-x86_64-3.5/_openssl.c -o build/temp.linux-x86_64-3.5/build/temp.linux-x86_64-3.5/_openssl.o -Wconversion -Wno-error=sign-conversion
�[39mbuild-basic-e2e-tests-image�[0m:	    build/temp.linux-x86_64-3.5/_openssl.c:22:24: fatal error: pyconfig.h: No such file or directory
�[39mbuild-basic-e2e-tests-image�[0m:	     #  include <pyconfig.h>
�[39mbuild-basic-e2e-tests-image�[0m:	                            ^
�[39mbuild-basic-e2e-tests-image�[0m:	    compilation terminated.
�[39mbuild-basic-e2e-tests-image�[0m:	    error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
�[39mbuild-basic-e2e-tests-image�[0m:	    
�[39mbuild-basic-e2e-tests-image�[0m:	    ----------------------------------------
�[39mbuild-basic-e2e-tests-image�[0m:	�[91mCommand "/usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-cmdb9o6x/cryptography/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-u98nk458-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-cmdb9o6x/cryptography/
�[39mbuild-basic-e2e-tests-image�[0m:	The command '/bin/sh -c pip3 install kubernetes' returned a non-zero code: 1
�[39mbuild-basic-e2e-tests-image�[0m:	�[0m

@IronPan
Copy link
Member Author

IronPan commented Feb 27, 2019

/test kubeflow-pipeline-e2e-test

@IronPan
Copy link
Member Author

IronPan commented Feb 27, 2019

/test kubeflow-pipeline-sample-test

@gaoning777
Copy link
Contributor

/lgtm

@IronPan
Copy link
Member Author

IronPan commented Feb 27, 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
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 18878f1 into kubeflow:master Feb 27, 2019
cheyang pushed a commit to alibaba/pipelines that referenced this pull request Mar 28, 2019
* update tests

* explicit return successful

* fix

* move variable

* Update deploy-kubeflow.sh
Linchin pushed a commit to Linchin/pipelines that referenced this pull request Apr 11, 2023
…#866)

* Add tekton tasks for eks-cluster-create/teardown and kaniko

* * increase default k8s version of eks-cluster-create task
* add sample file for aws-credentials secret

* rerun make optional-generate and make optional-test
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this pull request Mar 11, 2024
* Fix Tekton conditional dependency on sub-dag

* fix tekton conditional dependency on group ops
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