| Issue 3136: | com.google.gerrit.server.query.change.LuceneQueryChangesTest fails on CentOS 7 | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Affected Version: v2.10 This fails repeatedly. The smallest command line invocation I was able to come up with is `buck test //gerrit-server:query_tests --no-results-cache --num-threads 1`: FAIL 29.4s 32 Passed 0 Skipped 1 Failed com.google.gerrit.server.query.change.LuceneQueryChangesTest FAILURE byCommit: expected singleton List<ChangeInfo>, found [] for [6f5078cb5c4b22da7a260ecef5e8e1bab6904103] java.lang.AssertionError: expected singleton List<ChangeInfo>, found [] for [6f5078cb5c4b22da7a260ecef5e8e1bab6904103] at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at com.google.gerrit.server.query.change.AbstractQueryChangesTest.queryOne(AbstractQueryChangesTest.java:981) at com.google.gerrit.server.query.change.AbstractQueryChangesTest.byCommit(AbstractQueryChangesTest.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) 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.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.junit.runners.Suite.runChild(Suite.java:127) at org.junit.runners.Suite.runChild(Suite.java:26) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at org.junit.runner.JUnitCore.run(JUnitCore.java:138) at com.facebook.buck.junit.JUnitRunner.run(JUnitRunner.java:137) at com.facebook.buck.junit.JUnitRunner.main(JUnitRunner.java:420) [centos@c7-build gerrit]$ rpm -qa | grep jdk java-1.7.0-openjdk-1.7.0.75-2.5.4.2.el7_0.x86_64 java-1.7.0-openjdk-devel-1.7.0.75-2.5.4.2.el7_0.x86_64 java-1.7.0-openjdk-headless-1.7.0.75-2.5.4.2.el7_0.x86_64
Jan 28, 2015
#1
j...@flaska.net
Jan 28, 2015
This was discussed on repo-discuss ML: [1]. [1] https://groups.google.com/d/topic/repo-discuss/EA9stjeDmlE/discussion
Status:
AwaitingInformation
Jan 28, 2015
Doh, and I'm on that ML. Would you like me to check whether a backported patch fixes this for me, or is it considered not to be worth of backporting?
Jan 28, 2015
I think it worth to be backported.
Jan 28, 2015
(No comment was entered for this change.)
Status:
Submitted
Labels: FixedIn-2.10.1
Mar 19, 2015
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |