[
https://issues.apache.org/jira/browse/HADOOP-14500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041527#comment-16041527
]
Rajesh Balamohan commented on HADOOP-14500:
-------------------------------------------
It was simulation related I believe. When earlier patch results were submitted
“fs.contract.test.fs.wasb” was not added IIRC. So some of the tests were
getting ignored as mentioedn in. For the results posted here, I added all the
3 parameters mentioned in “fs.azure.test.account.name”,
“fs.azure.account.key.{ACCOUNTNAME}.blob.core.windows.net” and
“fs.contract.test.fs.wasb”.
Before HADOOP-14478, seek() was closing the inputstream explicitly and
re-opening it. With HADOOP-14478, it is not expected to do so. So seek need not
throw FNFE; however would throw this error in subsequent read.
> Azure: TestFileSystemOperationExceptionHandling{,MultiThreaded} fails
> ---------------------------------------------------------------------
>
> Key: HADOOP-14500
> URL: https://issues.apache.org/jira/browse/HADOOP-14500
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure, test
> Reporter: Mingliang Liu
> Assignee: Rajesh Balamohan
> Attachments: HADOOP-14500-001.patch
>
>
> The following test fails:
> {code}
> TestFileSystemOperationExceptionHandling.testSingleThreadBlockBlobSeekScenario
> Expected exception: java.io.FileNotFoundException
> TestFileSystemOperationsExceptionHandlingMultiThreaded.testMultiThreadBlockBlobSeekScenario
> Expected exception: java.io.FileNotFoundException
> {code}
> I did early analysis and found [HADOOP-14478] maybe the reason. I think we
> can fix the test itself here.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
