[WIP][SPARK-31902][K8S][TEST] Fix the K8s integration test Jenkins mockito errors #28722
Conversation
This file contains hidden or 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
…to see if we can fix the mockito errors
Member
Contributor
Author
|
Ah gotcha that makes sense. I was debugging the same issue but I was only seeing it in the K8s PRB. I'll close this if that revert has it covered :) |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
Member
|
Ah, okay. I wasn't sure if it's same thing :-) |
|
Test build #123513 has finished for PR 28722 at commit
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What changes were proposed in this pull request?
Try adding a specific compatable bytebuddy as an explicit dependency to see if we can fix the mockito errors
Why are the changes needed?
The Jenkin K8s PR builder is consistently failing with Mockito errors running through the core suite.
Does this PR introduce any user-facing change?
No
How was this patch tested?
I will run it through Jenkins and see if it fixes the issues.