[
https://issues.apache.org/jira/browse/HADOOP-13882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735044#comment-15735044
]
Steve Loughran commented on HADOOP-13882:
-
Looks like it's a time issue: the test run took too long and the timeout kicked
in before enough retries had run.
Maybe crank back to count > 2 (to imply more than one iteration), and for the
exception to be more meaningful
{code}
@Test
public void testAwaitAlwaysFalse() throws Throwable {
try {
await(TIMEOUT,
ALWAYS_FALSE,
retry,
TIMEOUT_FAILURE_HANDLER);
fail("should not have got here");
} catch (TimeoutException e) {
assertTrue(retry.getInvocationCount() > 4);
}
}
{code}
> TestLambdaTestUtils.testAwaitAlwaysFalse failing
>
>
> Key: HADOOP-13882
> URL: https://issues.apache.org/jira/browse/HADOOP-13882
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
>Affects Versions: 3.0.0-alpha2
>Reporter: Steve Loughran
>
> {{org.apache.hadoop.test.TestLambdaTestUtils.testAwaitAlwaysFalse}} failing
> on a Jenkins test run. No obvious info in the test as to why.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org