Fetching and logging Livy session logs for LivyOperator #17393
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sreenath-kamath
force-pushed
the
issue-17340
branch
from
0a0ae42 to
c01fb9b
Compare
collinmcnulty
approved these changes
Aug 20, 2021
|
For whatever it's worth, I ran the provider tests with python 3.6 and postgres 9.6 in breeze both on this commit and this after merging main back in and they pass. |
|
Transient error. no worres |
potiuk
approved these changes
Aug 20, 2021
45 tasks
56 tasks
54 tasks
91 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fetching and logging Livy session logs for LivyOperator
closes: #17340