You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benson Margulies (JIRA)" <ji...@codehaus.org> on 2013/01/28 20:33:13 UTC
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Benson Margulies created SUREFIRE-954:
-----------------------------------------
Summary: Hard-to-believe abstract method error
Key: SUREFIRE-954
URL: https://jira.codehaus.org/browse/SUREFIRE-954
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.13
Reporter: Benson Margulies
I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
{noformat}
Running com.basistech.TestLogCallback
0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
Exiting cleanup thread
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
java.lang.AbstractMethodError:
java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318265#comment-318265 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
I put a test case on a branch:
surefire-954-test
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318227#comment-318227 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
The intelliJ debugger cannot show me a value for 't' at all.
Any attempt to poke at it results in 'Invalid JNI Signature'
However, if I crawl up the stack to ForkedBooter line 104, I see that t is an InvocationTargetException.
t.getClass().getClassLoader() is null (!).
Here ends the first dispatch from the front.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318237#comment-318237 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
ProviderFactory confuses the debugger as well as ForkedBooter.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318234#comment-318234 ]
Kristian Rosenvold commented on SUREFIRE-954:
---------------------------------------------
Are you running with a security manager installed ?
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318270#comment-318270 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
Unfortunately, I have an additional frustration here. I can't repro the exception outside of Maven! If I run from IntelliJ, the test works fine. Also not that we get the exception trace after the Tests run: line.
It appears that attaching a debugger results in the inability to debug exceptions thrown inside of methods invoked with Method.invoke. My next attempt will be to set forkMode to never and try to just run mvnDebug and see what I see.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318219#comment-318219 ]
Kristian Rosenvold commented on SUREFIRE-954:
---------------------------------------------
Which jdk version are you running on ?
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318224#comment-318224 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
{noformat}
[benson] rlp/source/java-benchmark [java-benchmark:] % java -version
java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b04-413-12A269)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-413, mixed mode)
{noformat}
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318221#comment-318221 ]
Kristian Rosenvold commented on SUREFIRE-954:
---------------------------------------------
You /may/ have to open surefire source, set a breakpoint at LegacyPojoStackTraceWriter.java:54, run your test with -Dmaven.surefire.debug=true and attach a debugger to see WTF is going on here ;) I wonder what "t" is. Also, it may be "interesting" what you can find out about t's classloader; like inspecting t.getClass().getClassLoader(). /If/ the classloader is an "IsolatedClassLoader" it has a roleName attribute. I sure hope it's not the IsolatedClassLoader btw ;)
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318239#comment-318239 ]
Kristian Rosenvold commented on SUREFIRE-954:
---------------------------------------------
If you suspect this happens in one of your @BeforeClass methods (which makes sense), you might consider attaching a debugger with your OWN code and set breakpoints in ALL the @BeforeClass methods and step through them.
You can *also* try to force the JUnittCore provider just to smoke out the problem, since that has different exception handling for @BeforeClass stuff.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318285#comment-318285 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
My attempt at an IT to show this problem fails to show this problem, now that I look at it when I'm awake.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318233#comment-318233 ]
Kristian Rosenvold commented on SUREFIRE-954:
---------------------------------------------
It may help you to check out the tag of the surefire version you are running. Sorry for forgetting to mention ;
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318299#comment-318299 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
I can now describe the condition that triggers this behavior, but I suspect that it's more of a JVM issue than a JUnit or Surefire issue.
Some native code called DeleteGlobalRef on the wrong ref, and then tried to use it from within a native method from within an @After method. This caused the JVM to throw something -- I can't really figure out what, because neither Eclipse nor IntelliJ is very good at explaining it. That wierd exception gets picked up by reflection and packaged into the target of an InvocationTargetException, and everything goes downhill from there. It sure seems as if the JVM has picked an 'exotic' class loader to put it in, but I can't find any evidence.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318235#comment-318235 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
Kristian,
I pulled from git, I built, and I changed my pom to look for 2.14-SNAPSHOT. And the debugger is fine except for ForkedBooter.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318232#comment-318232 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
Now I've got a breakpoint on InvocationTargetException. Last hit before the problem, backtrace:
{noformat}
main@1, prio=5, in group 'main', status: 'RUNNING'
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:93)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)
{noformat}
Which purports to be on line:
{code}
System.setErr( orgSystemErr );
{code}
Which is a bit hard to believe. I think I'm being fooled by the shade technology.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318266#comment-318266 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
By the way, I was able to see enough contents of Method objects to identify my @BeforeClass method.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318238#comment-318238 ]
Kristian Rosenvold commented on SUREFIRE-954:
---------------------------------------------
I know intellij gets confused by classloaders/different sometimes. An alternate "solution" which will involve a little keypressing is to simply set exception breakpoints for "ANy exception" or "Invocation target exception" in the forked process to try to get to the source of the problem
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318236#comment-318236 ]
Benson Margulies commented on SUREFIRE-954:
-------------------------------------------
And I have no security manager. Plain old 'mvn' command line.
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-954) Hard-to-believe abstract method error
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318286#comment-318286 ]
Kristian Rosenvold commented on SUREFIRE-954:
---------------------------------------------
Yeah; we have a fairly decent IT coverage in surefire. Expect most of the easy ones to be taken ;)
> Hard-to-believe abstract method error
> -------------------------------------
>
> Key: SUREFIRE-954
> URL: https://jira.codehaus.org/browse/SUREFIRE-954
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Benson Margulies
>
> I have a set of junit test that I am running with Surefire 2.13 with forkMode always. Two classes die with the following hard-to-belive backtrace. The others are fine. Sadly, I can't open-source the test case, so I'm hoping that you will give me some advice as to how to be a remote-control debugging assistant to look into this. The AbstractMethodError is very hard for me to imagine explaining.
> {noformat}
> Running com.basistech.TestLogCallback
> 0 [main] DEBUG com.basistech.rlp.RLPEnvironment - Starting cleanup thread
> 6 [main] DEBUG com.basistech.rlp.RLPEnvironment - cleanupContext
> java.lang.ref.PhantomReference@509df6f1 7f9e59a073b0
> 6 [RLP Context Cleanup] DEBUG com.basistech.rlp.RLPEnvironment -
> Exiting cleanup thread
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
> java.lang.AbstractMethodError:
> java.lang.Throwable.printStackTrace(Ljava/io/PrintWriter;)V
> at org.apache.maven.surefire.report.LegacyPojoStackTraceWriter.writeTraceToString(LegacyPojoStackTraceWriter.java:54)
> at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:330)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:104)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira