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 issues with test_upgrade notebook #2145

Merged
merged 2 commits into from
Jul 20, 2020
Merged

fix issues with test_upgrade notebook #2145

merged 2 commits into from
Jul 20, 2020

Conversation

RafalSkolasinski
Copy link
Contributor

@RafalSkolasinski RafalSkolasinski commented Jul 16, 2020

What this PR does / why we need it:

It fixes problems with notebook that tests seldon-core upgrades.

Which issue(s) this PR fixes:

Closes #2119

Special notes for your reviewer:

  • increased timeout in waitStatus helper function (defined inside notebook)
  • fixed re-raising exception if notebook fails
  • fixed helm-target for upgrade command (makefile installs seldon, notebook was trying to upgrade seldon-core)
  • install_seldon target in testing Makefile can be re-executed now as it will first attempt to remove currently installed seldon-core

Does this PR introduce a user-facing change?:

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

Review Jupyter notebook visual diffs & provide feedback on notebooks.


Powered by ReviewNB

@seldondev
Copy link
Collaborator

Thu Jul 16 11:55:08 UTC 2020
The logs for [pr-build] [1] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/1.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=1

@seldondev
Copy link
Collaborator

Thu Jul 16 11:55:23 UTC 2020
The logs for [lint] [2] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/2.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=2

@RafalSkolasinski
Copy link
Contributor Author

/test notebooks
/test integration

@seldondev
Copy link
Collaborator

Thu Jul 16 11:58:38 UTC 2020
The logs for [integration] [4] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/4.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=4

@seldondev
Copy link
Collaborator

Thu Jul 16 11:58:42 UTC 2020
The logs for [notebooks] [3] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/3.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=3

@seldondev
Copy link
Collaborator

Thu Jul 16 12:49:32 UTC 2020
The logs for [lint] [6] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/6.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=6

@seldondev
Copy link
Collaborator

Thu Jul 16 12:49:38 UTC 2020
The logs for [pr-build] [5] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/5.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=5

@RafalSkolasinski
Copy link
Contributor Author

@axsaucedo Wondering if it wouldn't be reasonable for testing Makefile to helm install seldon-core instead of helm install seldon?

@RafalSkolasinski
Copy link
Contributor Author

Logs got garbage collected... starting tests again.
/test notebooks
/test integration

@seldondev
Copy link
Collaborator

Thu Jul 16 15:26:55 UTC 2020
The logs for [integration] [8] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/8.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=8

@seldondev
Copy link
Collaborator

Thu Jul 16 15:27:05 UTC 2020
The logs for [notebooks] [7] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/7.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=7

@axsaucedo
Copy link
Contributor

/test integration
/test notebooks

@seldondev
Copy link
Collaborator

Fri Jul 17 16:04:07 UTC 2020
The logs for [integration] [10] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/10.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=10

@seldondev
Copy link
Collaborator

Fri Jul 17 16:04:29 UTC 2020
The logs for [notebooks] [9] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/9.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=9

@axsaucedo
Copy link
Contributor

/test integration
/test notebooks

@seldondev
Copy link
Collaborator

Fri Jul 17 18:18:28 UTC 2020
The logs for [notebooks] [11] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/11.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=11

@seldondev
Copy link
Collaborator

Fri Jul 17 18:18:28 UTC 2020
The logs for [integration] [12] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/12.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=12

@RafalSkolasinski
Copy link
Contributor Author

Failure on: test_label_update[1.0.2]
Triggering integration tests again.

/test integration

@seldondev
Copy link
Collaborator

Mon Jul 20 10:00:21 UTC 2020
The logs for [integration] [13] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/13.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=13

@RafalSkolasinski
Copy link
Contributor Author

Failure on test_rolling_deployment[graph1.json-graph2.json-True-ambas] - different one
/test integration

@seldondev
Copy link
Collaborator

Mon Jul 20 10:55:45 UTC 2020
The logs for [integration] [14] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/14.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2145 --build=14

@RafalSkolasinski
Copy link
Contributor Author

And now it is TestPrepack.test_text_alibi_explainer.

Three runs, three different failures -> @axsaucedo can we consider it just flakiness?

@axsaucedo
Copy link
Contributor

@RafalSkolasinski yes, if you can run these three tests locally and confirm they pass I think it woudl be reasonable to go ahead, looking at cluster metrics it may be that we need to add more memory resources to the pods that run the integration + notebook tests

@RafalSkolasinski
Copy link
Contributor Author

RafalSkolasinski commented Jul 20, 2020

Nothing in this PR that could actually affect the tests in question.

Except maybe tiny modification here:
https://github.com/SeldonIO/seldon-core/pull/2145/files#diff-584998bbdce9ef98a2ec464ddfe71576R76
but this only make install_seldon target in the Makefile re-triggerable.

So basically running these three integration tests locally would be like running against master.

@RafalSkolasinski
Copy link
Contributor Author

/test integration

@seldondev
Copy link
Collaborator

STARTING TEST [ integration # 15 ]

Logs will be available when test completes in the following link:
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2145/15.log

Impatient try:
jx get build logs SeldonIO/seldon-core/PR-2145 --build=15

@axsaucedo
Copy link
Contributor

That's a good point, I think given that it has passed, and the notebooks test (which is the main one) has passed, we can merge
/approve

@seldondev
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: axsaucedo

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

@seldondev
Copy link
Collaborator

@RafalSkolasinski: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
integration 63a2274 link /test integration

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

@RafalSkolasinski RafalSkolasinski merged commit 6e9780f into SeldonIO:master Jul 20, 2020
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.

Robustness of operator_upgrade notebook
3 participants