[
https://issues.apache.org/jira/browse/IMPALA-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996603#comment-16996603
]
Tim Armstrong commented on IMPALA-8753:
---------------------------------------
Hit https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/9271/. It looks
like [~boroknagyz] wrote that originally so will assign to him.
> JdbcTest's testConcurrentSessionMixedIdleTimeout() flaky
> --------------------------------------------------------
>
> Key: IMPALA-8753
> URL: https://issues.apache.org/jira/browse/IMPALA-8753
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 3.3.0
> Reporter: Joe McDonnell
> Priority: Critical
> Labels: broken-build
>
> An exhaustive run on Centos6 hit a failure in
> JdbcTest::testConcurrentSessionMixedIdleTimeout():
>
> {noformat}
> 02:29:36 [ERROR] Tests run: 26, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 69.083 s <<< FAILURE! - in org.apache.impala.service.JdbcTest
> 02:29:36 [ERROR]
> testConcurrentSessionMixedIdleTimeout[0](org.apache.impala.service.JdbcTest)
> Time elapsed: 13.222 s <<< FAILURE!
> 02:29:36 at
> org.apache.impala.service.JdbcTest.testConcurrentSessionMixedIdleTimeout(JdbcTest.java:581)
> 02:29:36 at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
> ...
> 02:29:36 [ERROR] Failures:
> 02:29:36 [ERROR] JdbcTest.testConcurrentSessionMixedIdleTimeout:581
> expected:<0> but was:<1>
> 02:29:36 [ERROR] Tests run: 970, Failures: 1, Errors: 0, Skipped: 45{noformat}
> The faliure didn't produce much output (no JUnitXML, for example).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
