Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Verbose mode > 4 can crash with Maven failsafe

See original GitHub issue

This is weired. When running TestNG + Maven failesafe, with surefire.testng.verbose > 4:

<configuration>
    <suiteXmlFiles>
        <suiteXmlFile>My_Test_Suite.xml</suiteXmlFile>
    </suiteXmlFiles>
    <systemPropertyVariables>

        <surefire.security.manager>java.lang.SecurityManager</surefire.security.manager>
        <java.security.manager>default</java.security.manager>
    </systemPropertyVariables>

    <useSystemClassloader>false</useSystemClassloader>
    <threadCount>20</threadCount>
    <reuseForks>true</reuseForks>
    <argLine>-Xmx2048m</argLine>
    <properties>
        <property>
            <name>listener</name>
            <value>org.imaginea.jenkins.plugins.testinprogress.testng.TestNGProgressRunListener</value>
        </property>
        <property>
            <name>surefire.testng.verbose</name>
            <value>10</value>
        </property>
    </properties>
</configuration>

On Windows 2008 R2, all tests fail right away. If I change it to Verbose < 5, everything run as usual.

I’m not sure if the following exception is the cause:

Creating c:\jenkins-slave\workspace\Automation_Matrix_New\72b9012b\test-output\testng-failed.xml java.io.IOException: The filename, directory name, or volume label syntax is incorrect at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.createNewFile(File.java:1012) at org.testng.internal.Utils.writeFile(Utils.java:173) at org.testng.internal.Utils.writeUtf8File(Utils.java:135) at org.testng.reporters.FailedReporter.generateFailureSuite(FailedReporter.java:76) at org.testng.reporters.FailedReporter.generateReport(FailedReporter.java:47) at org.testng.TestNG.generateReports(TestNG.java:1135) at org.testng.TestNG.run(TestNG.java:1081) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:281) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:121) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

Issue Analytics

State:
Created 7 years ago
Comments:10 (1 by maintainers)

Top GitHub Comments

1reaction

cbeustcommented, Jun 16, 2016

This error doesn’t seem to be related to what I used to see (which is fixed in 6.9.11 as far as I can tell).

0reactions

juherrcommented, Jun 19, 2016

Ok, thank.

I had a look and the failing log is only activated with >4. I don’t understand what is the problem for the moment but feel free to analyse it 😃

Top Results From Across the Web

Maven Failsafe Plugin – Frequently Asked Questions

Alternatively the forked VM could also have crashed for a number of reasons. Look for the classical " hs_err* " files indicating VM...

maven failsafe with azure pipeline gives error - Stack Overflow

[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or ...

maven-failsafe-plugin fails on fork creation | Bitbucket Cloud

You could try running failsafe in non-forked mode, if you can, maybe that would give you a clue as to what's going on....

[ANN] Apache Maven Surefire/Failsafe Plugin Version 3.0.0 ...

[SUREFIRE-1945] - crashed tests - unit tests with large logging output does ... [SUREFIRE-1981] - Upgrade Apache maven-shared-utils to 3.3.4.

Building a Native Executable - Quarkus

You can provide custom options for the native-image command using the ... ms [INFO] [INFO] --- maven-failsafe-plugin:2.22.1:integration-test (default) ...