-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
HADOOP-16650. ITestS3AClosedFS failing -junit test thread. #1639
HADOOP-16650. ITestS3AClosedFS failing -junit test thread. #1639
Conversation
Change-Id: Ia58f5e1dd57588a28081f9c4092c010b3132856a
confirmed; fixes leaks. @bgaborg - could you take a look @ this? All I'm doing is stripping the junit and surefire threads out so they don't interfere with the results |
Yes, I'll take a look. |
thanks. full test run happy except for the root dir tests hinting that there was a test dir which shouldn't be there. All cleaned up and fsck is happy now :) |
given the usage of string literals instead of final fields in the environment of the method, I'm ok with this change. |
🎊 +1 overall
This message was automatically generated. |
I have a new failure during the test:
I don't think this is related. Any thoughts about this @steveloughran ? |
That is exactly what I saw. In the past that generally means some of the test with/without s3guard has put a tombstone above a path which has a file deep underneath. Our test runs are doing a dump of what's there iner target/, if you haven't done a maven clean yet you should be able to find the output |
This failure is not related but needs to be fixed. |
thanks, merged. |
Change-Id: Ia58f5e1dd57588a28081f9c4092c010b3132856a
tested: s3 ireland. now going to CP and test on the specific backport branch where I encountered the problem