hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-17024) Upgrade maven-surefire-plugin to version 2.19 or higher
Date Fri, 04 Nov 2016 17:11:58 GMT
Ted Yu created HBASE-17024:
------------------------------

             Summary: Upgrade maven-surefire-plugin to version 2.19 or higher
                 Key: HBASE-17024
                 URL: https://issues.apache.org/jira/browse/HBASE-17024
             Project: HBase
          Issue Type: Test
            Reporter: Ted Yu
            Priority: Minor


I was running two tests with the following specification:

-Dtest=TestWALLockup#testLockup16960,TestSyncFuture

I consistently got:
{code}
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.002 sec <<< FAILURE!
- in org.apache.hadoop.hbase.regionserver.TestWALLockup
org.apache.hadoop.hbase.regionserver.TestWALLockup  Time elapsed: 0.001 sec  <<<
ERROR!
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(String.java:1904)
	at org.apache.maven.surefire.junit4.JUnit4Provider.getMethod(JUnit4Provider.java:307)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:147)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)

Running org.apache.hadoop.hbase.regionserver.wal.TestSyncFuture
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.005 sec <<< FAILURE!
- in org.apache.hadoop.hbase.regionserver.wal.TestSyncFuture
org.apache.hadoop.hbase.regionserver.wal.TestSyncFuture  Time elapsed: 0.005 sec  <<<
ERROR!
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(String.java:1904)
	at org.apache.maven.surefire.junit4.JUnit4Provider.getMethod(JUnit4Provider.java:307)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:147)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
{code}
Turns out the above bug has been fixed by SUREFIRE-1161

We should consider upgrading maven-surefire-plugin to version 2.19 or higher.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message