-
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-17396. ABFS: testRenameFileOverExistingFile Fails after Contract test update #2491
Conversation
HNS-OAuth[INFO] Results: HNS-SharedKey[INFO] Results: NonHNS-SharedKey[INFO] Results: SAS Test failure is tracked in JIRA: https://issues.apache.org/jira/browse/HADOOP-17397 |
🎊 +1 overall
This message was automatically generated. |
Contributed by Sneha Vijayarajan. Change-Id: I57a866b95ff18229caee8a6028874074a29cb5bd
+1, merged to trunk and branch-3.3; sorry for this. I would have liked object store tests, but we can't insist on that for hadoop-common stuff. regarding the setup change, test teardown is meant to clean that up...what has probably happened is that the failure of the first attempt left things in a mess. Happens more to me when I'm working in an IDE and stopping test runs before getting to teardown(). Nothing wrong in adding the code though. |
…pache#2491) Contributed by Sneha Vijayarajan. Change-Id: I57a866b95ff18229caee8a6028874074a29cb5bd
Post updates to rename on existing file test, ABFS contract test is having failure. Updates were made in the AbstractContractTest class in https://issues.apache.org/jira/browse/HADOOP-17365.
To align to test expectation of no exception but a false return from rename, ABFS tests need config "fs.contract.rename-returns-false-if-dest-exists" set to true.
Also the abstract class was reusing a static test folder path. Hence on test re-run, where same storage container is used, source and destination path creations will fail with FileAlreadyExists, leading to test failures. This is also fixed.
[Test results pasted at the end of conversation tab].