OrDTesters created HBASE-21467:
----------------------------------
Summary: Fix flaky test
TestCoprocessorClassLoader.testCleanupOldJars
Key: HBASE-21467
URL: https://issues.apache.org/jira/browse/HBASE-21467
Project: HBase
Issue Type: Bug
Environment: Ubuntu 18.04 LTS
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T13:33:14-05:00)
Maven home: /home/OrdTesters/apache-maven-3.5.4
Java version: 1.8.0_172, vendor: Oracle Corporation, runtime:
/usr/lib/jvm/jdk1.8.0_172/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-36-generic", arch: "amd64", family: "unix"
Reporter: OrDTesters
TestCoprocessorClassLoader.testCleanupOldJars fails when run by itself.
This can be fixed by calling CoprocessorClassLoader.getClassLoader, which
initializes the jar file needed by testCleanupOldJars.
Pull request: to be added
Steps to reproduce:
{code:java}
git clone https://github.com/apache/hbase
cd hbase/hbase-common
mvn install -DskipTests -am
mvn test -Dtest="TestCoprocessorClassLoader#testCleanupOldJars"{code}
Stack trace of the failure:
{code:java}
java.io.FileNotFoundException:
/home/OrdTesters/Java/hbase/hbase-common/target/test-data/64b7e1ae-1c34-48f7-d731-9af59256dc0a/hbase-local-dir/jars/tmp/TestCleanupOldJars.test.jar
(Aucun fichier ou dossier de ce type) at java.io.FileOutputStream.open0(Native
Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at
java.io.FileOutputStream.<init>(FileOutputStream.java:213) at
java.io.FileOutputStream.<init>(FileOutputStream.java:162) at
org.apache.hadoop.hbase.util.TestCoprocessorClassLoader.testCleanupOldJars(TestCoprocessorClassLoader.java:65)
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:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
