[
https://issues.apache.org/jira/browse/HBASE-24123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086550#comment-17086550
]
Michael Stack commented on HBASE-24123:
---------------------------------------
This is w/ the 0.13 thrift:
{code}
[INFO] Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 110.869
s - in org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] TestThrift2HttpServer.testRunThriftServerWithHeaderBufferLength
Expected: (an instance of org.apache.thrift.transport.TTransportException and
exception with message a string containing "HTTP Response code: 431")
but: an instance of org.apache.thrift.transport.TTransportException
<java.lang.AssertionError: expected:<403> but was:<405>> is a
java.lang.AssertionError
Stacktrace was: java.lang.AssertionError: expected:<403> but was:<405>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:647)
at org.junit.Assert.assertEquals(Assert.java:633)
at
org.apache.hadoop.hbase.thrift.TestThriftHttpServer.checkHttpMethods(TestThriftHttpServer.java:210)
at
org.apache.hadoop.hbase.thrift.TestThriftHttpServer.runThriftServer(TestThriftHttpServer.java:178)
at
org.apache.hadoop.hbase.thrift.TestThriftHttpServer.testRunThriftServerWithHeaderBufferLength(TestThriftHttpServer.java:147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:258)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:288)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:282)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:748)
{code}
> [Flakey Tests] TestThrift?ServerCmdLine
> ---------------------------------------
>
> Key: HBASE-24123
> URL: https://issues.apache.org/jira/browse/HBASE-24123
> Project: HBase
> Issue Type: Bug
> Reporter: Michael Stack
> Priority: Major
>
> TestThrift2ServerCmdLine and TestThriftServerCmdLine are flakey. They fail
> frequently in local runs for myriad reasons: protocol failures, wrong answers
> on query, connection resets, etc. Each test runs 40 different combinations of
> config.
> This is after work done to try and stabilize by fixing port clash issues.
> Let me list in here the ways in which it fails. I will disable after I get a
> good list. Will also try and do some more stabilization too in sub-issues.
> Lets see which prevails; stabilization or disabling.
> For starters, this morning I got this:
> {code}
>
> -------------------------------------------------------------------------------
> Test set: org.apache.hadoop.hbase.thrift2.TestThrift2ServerCmdLine
>
> -------------------------------------------------------------------------------
> Tests run: 32, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 126.301 s
> <<< FAILURE! - in org.apache.hadoop.hbase.thrift2.TestThrift2ServerCmdLine
>
> org.apache.hadoop.hbase.thrift2.TestThrift2ServerCmdLine.testRunThriftServer[29]
> Time elapsed: 0.964 s <<< ERROR!
> java.lang.Exception: org.apache.thrift.transport.TTransportException:
> java.net.SocketException: Connection reset
> at
> org.apache.hadoop.hbase.thrift2.TestThrift2ServerCmdLine.talkToThriftServer(TestThrift2ServerCmdLine.java:92)
> Caused by: java.net.SocketException: Connection reset
> at
> org.apache.hadoop.hbase.thrift2.TestThrift2ServerCmdLine.talkToThriftServer(TestThrift2ServerCmdLine.java:92)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
