[jira] [Commented] (SUREFIRE-1382) OutOfMemoryError occurs when JUnit 5 test fails
[
https://issues.apache.org/jira/browse/SUREFIRE-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156925#comment-16156925
]
Mark Lagendijk commented on SUREFIRE-1382:
--
We just (yesterday) ran into this issue and finally found this bug report. We
wasted quite some time on analyzing the issue.
Based on this I am wondering: why is it that an bug which was solved nearly 2
months ago, has not yet been released?
> OutOfMemoryError occurs when JUnit 5 test fails
> ---
>
> Key: SUREFIRE-1382
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1382
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\prg\apache-maven-3.3.9\bin\..
> Java version: 1.8.0_102, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_102\jre
> Default locale: en_US, platform encoding: Cp1251
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
>Reporter: Oleksij Lupandin
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
>
> h4. Steps to reproduce
> # Check out project "maven-surefire2_20-junit5" from
> https://wissenst...@gitlab.com/wissenstein/maven-surefire2_20-junit5.git.
> # Go to the project root (where pom.xml is).
> # Run the following command: {code}mvn -Psurefire2_19_1 clean test{code}
> The project is tested using Surefire Maven plugin version 2.19.1. At the end
> of the output you can see:
> {code}---
> T E S T S
> ---
> Running com.wissenstein.mavensurefirejunit.SimplisticTest
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.073 sec <<<
> FAILURE! - in com.wissenstein.mavensurefirejunit.SimplisticTest
> shouldDeliberatelyFail() Time elapsed: 0.021 sec <<< FAILURE!
> org.opentest4j.AssertionFailedError: Test deliberately failed
> at
> com.wissenstein.mavensurefirejunit.SimplisticTest.shouldDeliberatelyFail(SimplisticTest.java:11)
> Results :
> Failed tests:
> SimplisticTest.shouldDeliberatelyFail:11 Test deliberately failed
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4.583 s
> [INFO] Finished at: 2017-06-06T16:57:35+02:00
> [INFO] Final Memory: 16M/264M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on
> project maven-surefire2_20-junit5: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\projects\surefire\maven-surefire2_20-junit5\target\surefire-reports for
> the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException{code}
> # Run the following command: {code}mvn -Psurefire2_20 clean test{code}
> The project is tested using Surefire Maven plugin version 2.20.
> h4. Actual result
> At the end of the output you can see: {code}[INFO]
> ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running com.wissenstein.mavensurefirejunit.SimplisticTest
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6.061 s
> [INFO] Finished at: 2017-06-06T17:03:52+02:00
> [INFO] Final Memory: 17M/3028M
> [INFO]
>
> [ERROR] Java heap space -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError{code}
> The stack trace is as follows: {code}java.lang.OutOfMemoryError: Java heap
> space
> at
[jira] [Commented] (SUREFIRE-1382) OutOfMemoryError occurs when JUnit 5 test fails
[
https://issues.apache.org/jira/browse/SUREFIRE-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157288#comment-16157288
]
Tibor Digana commented on SUREFIRE-1382:
Surefire will be released soon.
On Thu, Sep 7, 2017 at 3:00 PM, Mark Lagendijk (JIRA)
> OutOfMemoryError occurs when JUnit 5 test fails
> ---
>
> Key: SUREFIRE-1382
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1382
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\prg\apache-maven-3.3.9\bin\..
> Java version: 1.8.0_102, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_102\jre
> Default locale: en_US, platform encoding: Cp1251
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
>Reporter: Oleksij Lupandin
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
>
> h4. Steps to reproduce
> # Check out project "maven-surefire2_20-junit5" from
> https://wissenst...@gitlab.com/wissenstein/maven-surefire2_20-junit5.git.
> # Go to the project root (where pom.xml is).
> # Run the following command: {code}mvn -Psurefire2_19_1 clean test{code}
> The project is tested using Surefire Maven plugin version 2.19.1. At the end
> of the output you can see:
> {code}---
> T E S T S
> ---
> Running com.wissenstein.mavensurefirejunit.SimplisticTest
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.073 sec <<<
> FAILURE! - in com.wissenstein.mavensurefirejunit.SimplisticTest
> shouldDeliberatelyFail() Time elapsed: 0.021 sec <<< FAILURE!
> org.opentest4j.AssertionFailedError: Test deliberately failed
> at
> com.wissenstein.mavensurefirejunit.SimplisticTest.shouldDeliberatelyFail(SimplisticTest.java:11)
> Results :
> Failed tests:
> SimplisticTest.shouldDeliberatelyFail:11 Test deliberately failed
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4.583 s
> [INFO] Finished at: 2017-06-06T16:57:35+02:00
> [INFO] Final Memory: 16M/264M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on
> project maven-surefire2_20-junit5: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\projects\surefire\maven-surefire2_20-junit5\target\surefire-reports for
> the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException{code}
> # Run the following command: {code}mvn -Psurefire2_20 clean test{code}
> The project is tested using Surefire Maven plugin version 2.20.
> h4. Actual result
> At the end of the output you can see: {code}[INFO]
> ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running com.wissenstein.mavensurefirejunit.SimplisticTest
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6.061 s
> [INFO] Finished at: 2017-06-06T17:03:52+02:00
> [INFO] Final Memory: 17M/3028M
> [INFO]
>
> [ERROR] Java heap space -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError{code}
> The stack trace is as follows: {code}java.lang.OutOfMemoryError: Java heap
> space
> at java.util.Arrays.copyOf(Arrays.java:3332)
> at
> java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
> at
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157315#comment-16157315
]
Tibor Digana commented on SUREFIRE-1408:
[~aonishuk]
Attach current dump files and logs as files, but not in the Jira as comments.
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3030080908304903958tmp
> surefire_5025412729838224505067tmp
> [ERROR] Error occurred i
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157373#comment-16157373
]
Tibor Digana commented on SUREFIRE-1408:
[~aonishuk]
I guess this is OOM.
You have quite a lot tests and I guess the JVM exited. The logs tells me that
two test classes were aborted. The abort means that JVM finished abruptly and
did not finish test set. It's quite hard to confirm this but you can lookup
files generated by JVM {{java.hprof.txt}} or after segmentation fault
{{hs_err_pid*}}. If these are not found on the disk then configure JVM to write
dump file on OOM to disk. Printing GC with {{verbose:gc}} may help whats is
going on with Heap and PermGen. Please remove {{-X -e}} in commandline.
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye.
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157390#comment-16157390
]
Jonathan Hurley commented on SUREFIRE-1408:
---
[~tibor17] I've tried running the tests with up to 4GB of heap per JVM and it
doesn't help. I'll enable the heap dump options and try running them again to
see if I get anything generated from it.
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157422#comment-16157422
]
Tibor Digana commented on SUREFIRE-1408:
[~jonathan.hurley]
Java Heap might not be enough. Did you tune {{MaxPermSize}} on Java 6 or 7 and
{{MaxMetaSpace}} on Java 8.
Maybe you should use {{jconsole}}.
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire303008090830490
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157427#comment-16157427
]
Jonathan Hurley commented on SUREFIRE-1408:
---
No heap dumps were created on my last run (so I guess it's not an OOM for
heap). I'm using JDK 8 for these tests. I can try with {{MaxMetaSpace}} and see
if I get any different results. No dump files are created at all anywhere ...
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-ser
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157434#comment-16157434
]
Tibor Digana commented on SUREFIRE-1408:
What happens if you do not use groups?
${testcase.groups}
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3030080908304903958tmp
> surefire_5025412729838224505067tmp
> [ERROR] Error occurred in starting fork, check output i
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157473#comment-16157473
]
Jonathan Hurley commented on SUREFIRE-1408:
---
Specifying {{MaxMetaSpace}} didn't help. Trying it now without
{{testcase.groups}}...
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3030080908304903958tmp
> surefire_5025412729838224505067tmp
> [ERROR] Error occurre
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157513#comment-16157513
]
Tibor Digana commented on SUREFIRE-1408:
Do you use {{System.exit}} or {{Runtime.halt}} or {{FileDescriptor.out}} ?
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3030080908304903958tmp
> surefire_5025412729838224505067tmp
> [ERROR] Error occurred in starting fork
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157572#comment-16157572
]
Jonathan Hurley commented on SUREFIRE-1408:
---
[~tibor17] No change when removing {{testcase.groups}}.
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3030080908304903958tmp
> surefire_5025412729838224505067tmp
> [ERROR] Error occurred in starting fork, check outp
[jira] [Comment Edited] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157572#comment-16157572
]
Jonathan Hurley edited comment on SUREFIRE-1408 at 9/7/17 8:19 PM:
---
[~tibor17] No change when removing {{testcase.groups}}. The project has some
"System.exit()" calls from {{main()}} methods. We've commented all those out to
ensure it wasn't that.
We don't use the other calls.
was (Author: jonathan.hurley):
[~tibor17] No change when removing {{testcase.groups}}.
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/am
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157628#comment-16157628
]
Tibor Digana commented on SUREFIRE-1408:
[~aonishuk]
[~jonathan.hurley]
I have observed different result. I use Maven 3.5.0, JDK 1.8.0_144 and 16 GRAM.
This summary is from second run. The first run was without {{clean}} and {{-X}}
and {{-e}} but the summary was different and first two modules failed.
I did not see error in your tests.
I checked out the branch you told me as written in your post.
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Web . FAILURE [ 52.635 s]
[INFO] Ambari Views ... SUCCESS [ 6.327 s]
[INFO] utility SUCCESS [ 2.318 s]
[INFO] Ambari Metrics Common .. SUCCESS [ 8.940 s]
[INFO] Ambari Server .. FAILURE [04:42 min]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 05:53 min
[INFO] Finished at: 2017-09-07T22:44:53+02:00
[INFO] Final Memory: 53M/371M
[INFO]
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
(ambari-web unit tests) on project ambari-web: Command execution failed.
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (ambari-web unit tests)
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, chec
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157630#comment-16157630
]
Tibor Digana commented on SUREFIRE-1408:
This is my mvn options which includes memory setting for Maven process:
echo %MAVEN_OPTS%
-Dhttps.protocols="TLSv1" -server -Xmx768m -XX:MaxMetaspaceSize=864m
-Dmaven.repo.local=D:\.m2\repository
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157638#comment-16157638
]
Jonathan Hurley commented on SUREFIRE-1408:
---
I don't think that {{ambari-web}} is compatble with Maven 3.5.0 which is why it
failed. However, I can try just {{ambari-server}} with 3.5.0 and see if it
makes a difference...
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4
[jira] [Updated] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements
[ https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1383: --- Fix Version/s: (was: 2.20.1) 2.20.2 > dependenciesToScan Does Not Leverage Classpath Elements > > > Key: SUREFIRE-1383 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1383 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.20 >Reporter: Owen Farrell >Assignee: Tibor Digana > Fix For: 2.20.2 > > Attachments: scanned-dependencies-sample.zip > > Time Spent: 48h > Remaining Estimate: 24h > > The configuration attribute relies solely on installed > artifacts. This is an issue when the targeted dependencies were built as part > of the current session. The net result is that stale artifacts are used (i.e. > if the dependency has changed since it was last installed) or the tests are > not executed at all (if the dependency has not been previously installed. > Attached is a sample project that illustrates this issue: > Given I have a multi-module project >And the first module built includes test classes as part of the project > artifact >And subsequent modules scan the first for unit tests to execute > When I execute the _*test*_ goal (prior to any install) > Then the build should succeed >And tests should be executed with each module -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription
[
https://issues.apache.org/jira/browse/SUREFIRE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1372:
---
Fix Version/s: (was: 2.20.1)
2.20.2
> 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
> Fix For: 2.20.2
>
>
> 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
(v6.4.14#64029)
[jira] [Updated] (SUREFIRE-1373) Tests annotated with @NotThreadSafe are not executed in isolation
[ https://issues.apache.org/jira/browse/SUREFIRE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1373: --- Fix Version/s: (was: 2.20.1) 2.20.2 > Tests annotated with @NotThreadSafe are not executed in isolation > - > > Key: SUREFIRE-1373 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1373 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.20 >Reporter: Sebastian Kirsch >Assignee: Tibor Digana > Fix For: 2.20.2 > > Original Estimate: 48h > Remaining Estimate: 48h > > The [surefire > documentation|http://maven.apache.org/components/surefire/maven-failsafe-plugin/examples/fork-options-and-parallel-execution.html] > states that > bq. you can apply the JCIP annotation @net.jcip.annotations.NotThreadSafe on > the Java class of JUnit test (pure test class, Suite, Parameterized, etc.) in > order to execute it in single Thread instance. The Thread has name > maven-surefire-plugin@NotThreadSafe and it is executed at the end of the test > run. > However, the thread is run in parallel to the other tests being executed, > which contradicts the documentation and defeats the purpose of running tests > sequentially in a single thread. > See https://github.com/sebastiankirsch/surefire-nonthreadsafe for a test case. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SUREFIRE-1371) Plugin should fail if argLine is set when forkCount = 0
[
https://issues.apache.org/jira/browse/SUREFIRE-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1371:
---
Fix Version/s: (was: 2.20.1)
2.20.2
> Plugin should fail if argLine is set when forkCount = 0
>
>
> Key: SUREFIRE-1371
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1371
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin, process
> forking
>Reporter: Gili
>Assignee: Tibor Digana
> Fix For: 2.20.2
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Following up on SUREFIRE-1369: The plugin should fail with a verbose error if
> {{forkCount=0}} and {{}} is set.
> Per [~tibor17], this sanity check should happen in {{AbstractSurefireMojo}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SUREFIRE-1409) Parallel runner should not drop away runners that have zero children.
Tibor Digana created SUREFIRE-1409: -- Summary: Parallel runner should not drop away runners that have zero children. Key: SUREFIRE-1409 URL: https://issues.apache.org/jira/browse/SUREFIRE-1409 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.20.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SUREFIRE-1409) Parallel runner should not drop away runners that have zero children.
[ https://issues.apache.org/jira/browse/SUREFIRE-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1409: --- Issue Type: Improvement (was: Bug) > Parallel runner should not drop away runners that have zero children. > - > > Key: SUREFIRE-1409 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1409 > Project: Maven Surefire > Issue Type: Improvement > Components: Junit 4.7+ (parallel) support >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.20.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157673#comment-16157673
]
Jonathan Hurley commented on SUREFIRE-1408:
---
Maven 3.5.0 produced some extra output, but still crashed. If you just run the
test phase inside of {{ambari-server}} can you reproduce the issue?
{code}
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR] org.apache.ambari.server.orm.TestOrmImpl
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:292)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
...
[ERROR] Caused by:
org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM
terminated without properly saying goodbye. VM crash or System.exit called?
{code}
> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-2
[jira] [Updated] (SUREFIRE-1403) [Jigsaw] [Java 9] add "--add-modules ALL-SYSTEM" to forked CLI argument
[
https://issues.apache.org/jira/browse/SUREFIRE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1403:
---
Description:
Calling *findClass( cls, "java.se.ee")* in *IsolatedClassLoader* does not help
and does not do anything because the module is ignored in Java 9.
In-plugin provider does not have any problem to load classes from entire JDK.
Forked JVM would work only after added
{{--add-modules java.se.ee}}
The fix would be to add "--add-modules java.se.ee" if {{--add-modules}} is not
specified by user at Java 9+.
was:
Calling *findClass( cls, "java.se.ee")* in *IsolatedClassLoader* does not help
and does not do anything because the module is ignored in Java 9.
In-plugin provider does not have any problem to load classes from entire JDK.
Forked JVM would work only after added
{{--add-modules ALL-SYSTEM}}
The fix would be to add "--add-modules ALL-SYSTEM" if {{--add-modules}} is not
specified by user at Java 9+.
> [Jigsaw] [Java 9] add "--add-modules ALL-SYSTEM" to forked CLI argument
> ---
>
> Key: SUREFIRE-1403
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1403
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
> Attachments: surefire-1403.zip
>
>
> Calling *findClass( cls, "java.se.ee")* in *IsolatedClassLoader* does not
> help and does not do anything because the module is ignored in Java 9.
> In-plugin provider does not have any problem to load classes from entire JDK.
> Forked JVM would work only after added
> {{--add-modules java.se.ee}}
> The fix would be to add "--add-modules java.se.ee" if {{--add-modules}} is
> not specified by user at Java 9+.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SUREFIRE-1403) [Jigsaw] [Java 9] add "--add-modules java.se.ee" to forked CLI argument
[
https://issues.apache.org/jira/browse/SUREFIRE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1403:
---
Summary: [Jigsaw] [Java 9] add "--add-modules java.se.ee" to forked CLI
argument (was: [Jigsaw] [Java 9] add "--add-modules ALL-SYSTEM" to forked CLI
argument)
> [Jigsaw] [Java 9] add "--add-modules java.se.ee" to forked CLI argument
> ---
>
> Key: SUREFIRE-1403
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1403
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
> Attachments: surefire-1403.zip
>
>
> Calling *findClass( cls, "java.se.ee")* in *IsolatedClassLoader* does not
> help and does not do anything because the module is ignored in Java 9.
> In-plugin provider does not have any problem to load classes from entire JDK.
> Forked JVM would work only after added
> {{--add-modules java.se.ee}}
> The fix would be to add "--add-modules java.se.ee" if {{--add-modules}} is
> not specified by user at Java 9+.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1409) Parallel runner should not drop away runners that have zero children.
[ https://issues.apache.org/jira/browse/SUREFIRE-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157772#comment-16157772 ] ASF GitHub Bot commented on SUREFIRE-1409: -- Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/114 https://issues.apache.org/jira/browse/SUREFIRE-1409 > Parallel runner should not drop away runners that have zero children. > - > > Key: SUREFIRE-1409 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1409 > Project: Maven Surefire > Issue Type: Improvement > Components: Junit 4.7+ (parallel) support >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.20.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DOXIA-492) Add support for doxia macros in markdown documents.
[
https://issues.apache.org/jira/browse/DOXIA-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157848#comment-16157848
]
Hervé Boutemy commented on DOXIA-492:
-
[~spyhunter99]please create another Jira issue: this issue is closed
> Add support for doxia macros in markdown documents.
> ---
>
> Key: DOXIA-492
> URL: https://issues.apache.org/jira/browse/DOXIA-492
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Markdown
>Affects Versions: 1.4
>Reporter: Juergen Kellerer
>Assignee: Hervé Boutemy
> Fix For: 1.7
>
> Attachments: maven-site-plugin-integration-test.patch, screen.png
>
>
> It would be nice if doxia macros could be supported also inside markdown
> documents (similar to APT).
> Existing macros (especially snippet) is very useful, however with the power
> of maven there's the ability to register own macros for a build process which
> enables reuse of resources and improves dryness in general.
> A syntax which may work could be the following:
> * Block Level
> {noformat}
>#`??MACRO_NAME MACRO_ARGS`
> {noformat}
> * Inline
> {noformat}
> `??MACRO_NAME MACRO_ARGS`
> {noformat}
> Reference:
> http://hackage.haskell.org/packages/archive/yesod-markdown/0.0/doc/html/Yesod-Markdown-Macros.html
> E.g. using "Texts" it works just from the Editor:
> !screen.png!
> When macros are not interpreted, they fallback to a code block, thus it's
> easy to edit these sort of documents with one of the existing nice markdown
> editors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MSITE-748) EmptyStackException on xdoc toc macro usage
[
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157843#comment-16157843
]
Hervé Boutemy commented on MSITE-748:
-
sorry, I completely missed the new interest in this issue
when you talk about , I don't see who it is related to xdoc Doxia markup:
are you using Markdown?
should we create a separate Jira issue?
because one of the cause of me missing this issue is that it is related to
xdoc: AFAIK, it is not a markup that is widely used nowadays
But if we have an issue with Markdown markup, the issue gets bigger. And the
solution is not the same: Markdown support uses xhtml internally (not xdoc).
sharing a sample project would really be useful to work together, whatever the
root cause is: I'll see if another Jira issue is useful
> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro
> like this:
> {code}
>
>
>
>
>
>
>
>
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating:
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING] was already defined in , ignored in
> .
> [DEBUG] Unrecognized xdoc tag: at [17:70]
> [DEBUG] Unrecognized xdoc tag: at [18:76]
> [warn] was already defined in , ignored in .
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
> checkstyle: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
> project checkstyle: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-site of goal org.apache.ma
[jira] [Updated] (DOXIA-533) title in xdoc source cause wrong output (and make toc macro fail)
[
https://issues.apache.org/jira/browse/DOXIA-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated DOXIA-533:
Summary: title in xdoc source cause wrong output (and make toc
macro fail) (was: title in source cause wrong output (and make toc
macro fail))
> title in xdoc source cause wrong output (and make toc macro fail)
> --
>
> Key: DOXIA-533
> URL: https://issues.apache.org/jira/browse/DOXIA-533
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Xdoc
>Affects Versions: 1.6
>Reporter: Hervé Boutemy
>
> as discovered while working on MSITE-748, {{}} should not immediately
> close the subsection, but just stop taking text as title, then continue with
> subsection content
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (DOXIA-492) Add support for doxia macros in markdown documents.
[
https://issues.apache.org/jira/browse/DOXIA-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990803#comment-15990803
]
Hervé Boutemy edited comment on DOXIA-492 at 9/7/17 11:25 PM:
--
{noformat}Caused by: java.util.EmptyStackException
at java.util.Stack.peek(Unknown Source)
at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
at
org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874)
at
org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
at
org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
at org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
at
org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:263)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
at
org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
at
org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownParser.java:112
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
at
org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more{noformat}
was (Author: spyhunter99):
Caused by: java.util.EmptyStackException
at java.util.Stack.peek(Unknown Source)
at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
at org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:87
4)
at org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBasePar
ser.java:783)
at org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlP
arser.java:254)
at org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlPars
er.java:145)
at org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.j
ava:96)
at org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.jav
a:356)
at org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
at org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractPar
ser.java:136)
at org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlPar
ser.java:268)
at org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlPa
rser.java:233)
at org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlP
arser.java:263)
at org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlPars
er.java:145)
at org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.j
ava:96)
at org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.jav
a:356)
at org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownP
arser.java:112)
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocumen
t(DefaultSiteRenderer.java:449)
at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocum
ent(DoxiaDocumentRenderer.java:53)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(Defaul
tSiteRenderer.java:337)
at org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(Si
teMojo.java:262)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale(Si
[jira] [Created] (DOXIA-559) Doxia macro fails with markdown headers past level 4
Alex O'Ree created DOXIA-559: Summary: Doxia macro fails with markdown headers past level 4 Key: DOXIA-559 URL: https://issues.apache.org/jira/browse/DOXIA-559 Project: Maven Doxia Issue Type: Bug Reporter: Alex O'Ree see DOXIA-492 attempting to include the TOC using a markdown file. If you have any headers past level 3, the TOC fails using maven site plugin version 3.6, which looks like it's using doxia 1.7.4a I c&p'd http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-markdown/src/test/resources/macro-toc.md?view=markup&pathrev=1716285#l2 however no TOC is outputted on a test.md.vm file. If I change the file name to test.md (dropping the vm extension), I get a stack dump. "EmtpyStackException" when rendering this file. Not sure what I'm doing wrong Caused by: java.util.EmptyStackException at java.util.Stack.peek(Unknown Source) at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292) at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239) at org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874) at org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783) at org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254) at org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145) at org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96) at org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356) at org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117) at org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136) at org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268) at org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233) at org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:263) at org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145) at org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96) at org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356) at org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownParser.java:112 at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449) at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337) at org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262) at org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168) at org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) ... 21 more -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPDF-81) Override the copyright footer
[ https://issues.apache.org/jira/browse/MPDF-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157880#comment-16157880 ] Alex O'Ree commented on MPDF-81: ASF committer here, who can I lobby to get write access to this repo? FYI, I've forked this plugin and merged the needed doxia code into a single git repo and have charged forward with this and have published the changes to central. For anyone else that's interested and for consideration to merging back into the asf baseline https://github.com/spyhunter99/maven-pdf-plugin > Override the copyright footer > - > > Key: MPDF-81 > URL: https://issues.apache.org/jira/browse/MPDF-81 > Project: Maven PDF Plugin > Issue Type: New Feature >Affects Versions: 1.3 >Reporter: Alex O'Ree > > As of right now, it doesn't look possible to override the content of the > footer which is on all non-title page pages. It currently reads (c) year - > organization All rights reserved. > I don't see anywhere in the code where this is defined or in any of the > resource files. It is in the generated fo files but it's not obvious where > the xslt is. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPDF-81) Override the copyright footer
[ https://issues.apache.org/jira/browse/MPDF-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157966#comment-16157966 ] Hervé Boutemy commented on MPDF-81: --- I'll work with you on this: once we're successful for one issue and we're confident Maven conventions are known, I'll work with the team to have you committer so you can be autonomous to work on other issues I had a look on your GitHub repo: it's not forked from https://github.com/apache/maven-plugins , then it's not easy to define what to merge can you either create a patch to attach to Jira or prepare a GitHub PR for https://github.com/apache/maven-plugins , please? > Override the copyright footer > - > > Key: MPDF-81 > URL: https://issues.apache.org/jira/browse/MPDF-81 > Project: Maven PDF Plugin > Issue Type: New Feature >Affects Versions: 1.3 >Reporter: Alex O'Ree > > As of right now, it doesn't look possible to override the content of the > footer which is on all non-title page pages. It currently reads (c) year - > organization All rights reserved. > I don't see anywhere in the code where this is defined or in any of the > resource files. It is in the generated fo files but it's not obvious where > the xslt is. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DOXIA-559) Doxia macro fails with markdown headers past level 4
[ https://issues.apache.org/jira/browse/DOXIA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated DOXIA-559: Component/s: Module - Markdown > Doxia macro fails with markdown headers past level 4 > > > Key: DOXIA-559 > URL: https://issues.apache.org/jira/browse/DOXIA-559 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Markdown >Reporter: Alex O'Ree > > see DOXIA-492 > attempting to include the TOC using a markdown file. If you have any headers > past level 3, the TOC fails > using maven site plugin version 3.6, which looks like it's using doxia 1.7.4a > I c&p'd > http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-markdown/src/test/resources/macro-toc.md?view=markup&pathrev=1716285#l2 > however no TOC is outputted on a test.md.vm file. > If I change the file name to test.md (dropping the vm extension), I get a > stack dump. "EmtpyStackException" when rendering this file. Not sure what I'm > doing wrong > Caused by: java.util.EmptyStackException > at java.util.Stack.peek(Unknown Source) > at > org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292) > at > org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239) > at > org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874) > at > org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783) > at > org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254) > at > org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145) > at > org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96) > at > org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356) > at > org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117) > at > org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136) > at > org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268) > at > org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233) > at > org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:263) > at > org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145) > at > org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96) > at > org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356) > at > org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownParser.java:112 > at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449) > at > org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337) > at > org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262) > at > org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168) > at > org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > ... 21 more -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DOXIA-559) Doxia macro fails with markdown headers past level 4
[
https://issues.apache.org/jira/browse/DOXIA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated DOXIA-559:
Description:
attempting to include the TOC using a markdown file. If you have any headers
past level 3, the TOC fails
using maven site plugin version 3.6, which looks like it's using doxia 1.7.4a
I c&p'd
http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-markdown/src/test/resources/macro-toc.md?view=markup&pathrev=1716285#l2
however no TOC is outputted on a test.md.vm file.
If I change the file name to test.md (dropping the vm extension), I get a stack
dump. "EmtpyStackException" when rendering this file. Not sure what I'm doing
wrong
{noformat}Caused by: java.util.EmptyStackException
at java.util.Stack.peek(Unknown Source)
at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
at
org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874)
at
org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
at
org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
at org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
at
org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:263)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
at
org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
at
org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownParser.java:112
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
at
org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more{noformat}
was:
see DOXIA-492
attempting to include the TOC using a markdown file. If you have any headers
past level 3, the TOC fails
using maven site plugin version 3.6, which looks like it's using doxia 1.7.4a
I c&p'd
http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-markdown/src/test/resources/macro-toc.md?view=markup&pathrev=1716285#l2
however no TOC is outputted on a test.md.vm file.
If I change the file name to test.md (dropping the vm extension), I get a stack
dump. "EmtpyStackException" when rendering this file. Not sure what I'm doing
wrong
Caused by: java.util.EmptyStackException
at java.util.Stack.peek(Unknown Source)
at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
at
org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874)
at
org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
at
org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
at org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
at
org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268)
at
org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233)
at
org
[jira] [Commented] (DOXIA-492) Add support for doxia macros in markdown documents.
[
https://issues.apache.org/jira/browse/DOXIA-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157977#comment-16157977
]
Hervé Boutemy commented on DOXIA-492:
-
ok, I see DOXIA-559 was created
> Add support for doxia macros in markdown documents.
> ---
>
> Key: DOXIA-492
> URL: https://issues.apache.org/jira/browse/DOXIA-492
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Markdown
>Affects Versions: 1.4
>Reporter: Juergen Kellerer
>Assignee: Hervé Boutemy
> Fix For: 1.7
>
> Attachments: maven-site-plugin-integration-test.patch, screen.png
>
>
> It would be nice if doxia macros could be supported also inside markdown
> documents (similar to APT).
> Existing macros (especially snippet) is very useful, however with the power
> of maven there's the ability to register own macros for a build process which
> enables reuse of resources and improves dryness in general.
> A syntax which may work could be the following:
> * Block Level
> {noformat}
>#`??MACRO_NAME MACRO_ARGS`
> {noformat}
> * Inline
> {noformat}
> `??MACRO_NAME MACRO_ARGS`
> {noformat}
> Reference:
> http://hackage.haskell.org/packages/archive/yesod-markdown/0.0/doc/html/Yesod-Markdown-Macros.html
> E.g. using "Texts" it works just from the Editor:
> !screen.png!
> When macros are not interpreted, they fallback to a code block, thus it's
> easy to edit these sort of documents with one of the existing nice markdown
> editors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MSITE-748) EmptyStackException on xdoc toc macro usage
[
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157981#comment-16157981
]
Hervé Boutemy commented on MSITE-748:
-
DOXIA-559 created for issues on Markdown headers with TOC
> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro
> like this:
> {code}
>
>
>
>
>
>
>
>
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating:
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING] was already defined in , ignored in
> .
> [DEBUG] Unrecognized xdoc tag: at [17:70]
> [DEBUG] Unrecognized xdoc tag: at [18:76]
> [warn] was already defined in , ignored in .
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
> checkstyle: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
> project checkstyle: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site
> failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.util.EmptyStackException
> at java.util.Stack.peek(Stack.java:102)
> at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
> at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
> at
> org.apache.maven.doxia.module.x
[jira] [Updated] (DOXIA-559) Doxia macro fails with markdown headers past level 4
[
https://issues.apache.org/jira/browse/DOXIA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated DOXIA-559:
Affects Version/s: 1.7
> Doxia macro fails with markdown headers past level 4
>
>
> Key: DOXIA-559
> URL: https://issues.apache.org/jira/browse/DOXIA-559
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Affects Versions: 1.7
>Reporter: Alex O'Ree
>
> attempting to include the TOC using a markdown file. If you have any headers
> past level 3, the TOC fails
> using maven site plugin version 3.6, which looks like it's using doxia 1.7.4a
> I c&p'd
> http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-markdown/src/test/resources/macro-toc.md?view=markup&pathrev=1716285#l2
> however no TOC is outputted on a test.md.vm file.
> If I change the file name to test.md (dropping the vm extension), I get a
> stack dump. "EmtpyStackException" when rendering this file. Not sure what I'm
> doing wrong
> {noformat}Caused by: java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at
> org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
> at
> org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
> at
> org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at
> org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
> at
> org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:263)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at
> org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownParser.java:112
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DOXIA-559) Doxia macro fails with markdown headers past level 4
[
https://issues.apache.org/jira/browse/DOXIA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated DOXIA-559:
Attachment: toc-macro-test.md
sorry, I could not reproduce any failure: here is a test Markdown source I
simply added to a site (in {{src/site/markdown}} directory), then {{mvn site}}
does not fail and output is exactly as expected
please provide a sample test that show the failure
(notice that in a {{.vm}} file, hash have a Velocity meaning, then you have to
escape: this was an issue reported in MSITE-728 for which I added
DOXIASITETOOLS-133 feature to dump result after Velocity processing but before
Doxia rendering exactly to debug issues with Markdown+Velocity)
> Doxia macro fails with markdown headers past level 4
>
>
> Key: DOXIA-559
> URL: https://issues.apache.org/jira/browse/DOXIA-559
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Affects Versions: 1.7
>Reporter: Alex O'Ree
> Attachments: toc-macro-test.md
>
>
> attempting to include the TOC using a markdown file. If you have any headers
> past level 3, the TOC fails
> using maven site plugin version 3.6, which looks like it's using doxia 1.7.4a
> I c&p'd
> http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-markdown/src/test/resources/macro-toc.md?view=markup&pathrev=1716285#l2
> however no TOC is outputted on a test.md.vm file.
> If I change the file name to test.md (dropping the vm extension), I get a
> stack dump. "EmtpyStackException" when rendering this file. Not sure what I'm
> doing wrong
> {noformat}Caused by: java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at
> org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
> at
> org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
> at
> org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at
> org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
> at
> org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:263)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at
> org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownParser.java:112
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (DOXIA-559) Doxia macro fails with markdown headers past level 4
[
https://issues.apache.org/jira/browse/DOXIA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158005#comment-16158005
]
Hervé Boutemy edited comment on DOXIA-559 at 9/8/17 2:00 AM:
-
[~ste...@apache.org] [~spyhunter99] sorry, I could not reproduce any failure:
here is a test Markdown source I simply added to a site (in
{{src/site/markdown}} directory), then {{mvn site}} does not fail and output is
exactly as expected
please provide a sample test that show the failure
(notice that in a {{.vm}} file, hash have a Velocity meaning, then you have to
escape: this was an issue reported in MSITE-728 for which I added
DOXIASITETOOLS-133 feature to dump result after Velocity processing but before
Doxia rendering exactly to debug issues with Markdown+Velocity)
was (Author: hboutemy):
sorry, I could not reproduce any failure: here is a test Markdown source I
simply added to a site (in {{src/site/markdown}} directory), then {{mvn site}}
does not fail and output is exactly as expected
please provide a sample test that show the failure
(notice that in a {{.vm}} file, hash have a Velocity meaning, then you have to
escape: this was an issue reported in MSITE-728 for which I added
DOXIASITETOOLS-133 feature to dump result after Velocity processing but before
Doxia rendering exactly to debug issues with Markdown+Velocity)
> Doxia macro fails with markdown headers past level 4
>
>
> Key: DOXIA-559
> URL: https://issues.apache.org/jira/browse/DOXIA-559
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Affects Versions: 1.7
>Reporter: Alex O'Ree
> Attachments: toc-macro-test.md
>
>
> attempting to include the TOC using a markdown file. If you have any headers
> past level 3, the TOC fails
> using maven site plugin version 3.6, which looks like it's using doxia 1.7.4a
> I c&p'd
> http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-markdown/src/test/resources/macro-toc.md?view=markup&pathrev=1716285#l2
> however no TOC is outputted on a test.md.vm file.
> If I change the file name to test.md (dropping the vm extension), I get a
> stack dump. "EmtpyStackException" when rendering this file. Not sure what I'm
> doing wrong
> {noformat}Caused by: java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at
> org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
> at
> org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
> at
> org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at
> org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
> at
> org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:263)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at
> org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownParser.java:112
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
