-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-19184. S3A Fix TestStagingCommitter.testJobCommitFailure #6843
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
Conversation
Follow up of HADOOP-18679
|
not yet ready. will clean this up and retest. |
|
🎊 +1 overall
This message was automatically generated. |
|
I can only trigger the failure on trunk in a parallel test run! this explains why yetus missed it. except: I can also trigger it from the IDE, which isn't parallel. I don't understand this. Except to note that with this patch, even parallel runs are happy. |
|
Tested using us-west-1 bucket. All good. |
|
🎊 +1 overall
This message was automatically generated. |
steveloughran
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1. If we did more mocking we could do something more sophisticated/reusable, but it'd still be really brittle...
|
I was trying to do the mocking of the whole S3AStore but was unsuccessful. It was getting complicated without a working solution. maybe we can revisit it later. I think it will be required in the future. |
Follow up on HADOOP-18679 Contributed by: Mukund Thakur
|
w.r.t mocking we'd have a S3AFilesystem.createStore() method to create it, the mocking could do its work there, maybe by invoking superclass then mocking the operations it needs to. |
Yes, something like that. |
Follow up of HADOOP-18679
Description of PR
How was this patch tested?
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?