-
Notifications
You must be signed in to change notification settings - Fork 831
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
fix issues with test_upgrade notebook #2145
Conversation
Check out this pull request on Review Jupyter notebook visual diffs & provide feedback on notebooks. Powered by ReviewNB |
Thu Jul 16 11:55:08 UTC 2020 impatient try |
Thu Jul 16 11:55:23 UTC 2020 impatient try |
/test notebooks |
Thu Jul 16 11:58:38 UTC 2020 impatient try |
Thu Jul 16 11:58:42 UTC 2020 impatient try |
Thu Jul 16 12:49:32 UTC 2020 impatient try |
Thu Jul 16 12:49:38 UTC 2020 impatient try |
@axsaucedo Wondering if it wouldn't be reasonable for testing Makefile to |
Logs got garbage collected... starting tests again. |
Thu Jul 16 15:26:55 UTC 2020 impatient try |
Thu Jul 16 15:27:05 UTC 2020 impatient try |
/test integration |
Fri Jul 17 16:04:07 UTC 2020 impatient try |
Fri Jul 17 16:04:29 UTC 2020 impatient try |
/test integration |
Fri Jul 17 18:18:28 UTC 2020 impatient try |
Fri Jul 17 18:18:28 UTC 2020 impatient try |
Failure on: /test integration |
Mon Jul 20 10:00:21 UTC 2020 impatient try |
Failure on |
Mon Jul 20 10:55:45 UTC 2020 impatient try |
And now it is Three runs, three different failures -> @axsaucedo can we consider it just flakiness? |
@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 |
Nothing in this PR that could actually affect the tests in question. Except maybe tiny modification here: So basically running these three integration tests locally would be like running against master. |
/test integration |
STARTING TEST [ integration # 15 ]Logs will be available when test completes in the following link: Impatient try: |
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 |
[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 |
@RafalSkolasinski: The following test failed, say
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. |
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:
waitStatus
helper function (defined inside notebook)seldon
, notebook was trying to upgradeseldon-core
)install_seldon
target in testing Makefile can be re-executed now as it will first attempt to remove currently installed seldon-coreDoes this PR introduce a user-facing change?: