[ https://issues.apache.org/jira/browse/SUREFIRE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351896#comment-16351896 ]
ASF GitHub Bot commented on SUREFIRE-1372: ------------------------------------------ Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/150 Now there is only one issue to fix related to Windows paths. Need to investigate. https://builds.apache.org/job/maven-surefire-pipeline/job/SUREFIRE-1463/121 [windows-jdk9-maven3.5.x] shouldMatchSimpleClassNameAndMethodWithJavaExtWildcardPkg[0](org.apache.maven.surefire.its.TestMultipleMethodPatternsTestNGIT) On Sun, Feb 4, 2018 at 9:06 PM, Tibor Digana <tibordig...@apache.org> wrote: > The project has new build script and testing JDK 7-10 in combination of > multiple platforms. That is the main purpose of Version 2.21.0. Sorry that > it takes so long. We are discovering issues and fixing them one by one. I > think we are close to the end. > > On Fri, Feb 2, 2018 at 4:02 PM, hemachandraraok <notificati...@github.com> > wrote: > >> Sure and let me wait!!!!! >> Thank you so much for the updates!!!Cheers!!!!! >> >> — >> You are receiving this because you were mentioned. >> Reply to this email directly, view it on GitHub >> <https://github.com/apache/maven-surefire/pull/150#issuecomment-362610229>, >> or mute the thread >> <https://github.com/notifications/unsubscribe-auth/AA_yR4VCbLtVu6ypblIkJm7ZSxUbmhBGks5tQyOcgaJpZM4NoCQj> >> . >> > > > Rerunning failing tests fails in combination with > Description#createSuiteDescription > ------------------------------------------------------------------------------------ > > Key: SUREFIRE-1372 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1372 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin > Affects Versions: 2.20 > Reporter: M.P. Korstanje > Assignee: Tibor Digana > Priority: Major > Fix For: 2.21.0.Jigsaw > > > When using surefire to rerun failing tests created by a Runner that uses > {noformat}Description#createSuiteDescription{noformat} with a human readable > name rather then a class name the following stack trace occurs: > {code} > org.apache.maven.surefire.testset.TestSetFailedException: Unable to create > test class 'Scenario: Fail when running' > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)