[ https://issues.apache.org/jira/browse/HADOOP-16186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792902#comment-16792902
]
Gabor Bota commented on HADOOP-16186:
-------------------------------------
{quote}There's clearly some codepath which can surface which is causing failures in some situations,
and having multiple patches switching between the && and || operators isn't going
to to fix it
{quote}
You are right, but we need the find a way to reproduce it and write a test for it - find
that code path.
I cannot reproduce the issue simply by running the tests.
> NPE in ITestS3AFileSystemContract teardown in DynamoDBMetadataStore.lambda$listChildren
> ----------------------------------------------------------------------------------------
>
> Key: HADOOP-16186
> URL: https://issues.apache.org/jira/browse/HADOOP-16186
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Assignee: Gabor Bota
> Priority: Major
>
> Test run options. NPE in test teardown
> {code}
> -Dparallel-tests -DtestsThreadCount=6 -Ds3guard -Ddynamodb
> {code}
> If you look at the code, its *exactly* the place fixed in HADOOP-15827, a change which
HADOOP-15947 reverted.
> There's clearly some codepath which can surface which is causing failures in some situations,
and having multiple patches switching between the && and || operators isn't going
to to fix it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org
|