[
https://issues.apache.org/jira/browse/MNG-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776163#comment-16776163
]
Hervé Boutemy edited comment on MNG-6598 at 2/24/19 9:02 AM:
-------------------------------------------------------------
great news that this AnsiMain helps digging into Jansi questionning without
being polluted by any integration into any (complex) tool
if you're convinced that this Jansi throughput test performance is relevant,
measuring the perf without Jansi before measuring it with Jansi could be
useful, to see Jansi overhead.
On explaining the difference, between Jansi 1.16 and 1.17, the internal of
Jansi completely changed to better manage encoding: it's the addition of
PrintStream based implementation in
https://github.com/fusesource/jansi/commit/d340856e78925269ecc76cd16c29850fa9ca01e0
what you can test is the difference of performance of the old OutputStream
returned by AnsiConsole.wrapOutputStream(...) vs the performance of the new
AnsiConsole.wrapSystemOut(...): if the difference in performance is visible in
1.18-SNAPSHOT, we'll know that this is the right place to improve
was (Author: hboutemy):
great news that this AnsiMain helps digging into Jansi questionning without
being polluted by any integration into any (complex) tool
if you're convinced that this Jansi throughput test performance is relevant,
measuring the perf without Jansi before measuring it with Jansi could be
useful, to see Jansi overhead.
On explaining the difference, between Jansi 1.16 and 1.17, the internal of
Jansi completely changed to better manage encoding: it's the addition of
PrintStream based implementation in
https://github.com/fusesource/jansi/commit/d340856e78925269ecc76cd16c29850fa9ca01e0
what you can test is the difference of performance of the old OutputStream
returned by AnsiConsole.wrapOutputStream(...) vs the performance of the new
AnsiConsole.wrapSystemOut(...): if the difference in performance is the same in
1.18-SNAPSHOT, we'll know that this is the right place to improve
> Maven 3.6.0 and Surefire problem
> --------------------------------
>
> Key: MNG-6598
> URL: https://issues.apache.org/jira/browse/MNG-6598
> Project: Maven
> Issue Type: Task
> Components: General
> Affects Versions: 3.6.0
> Environment: windows 7, 64bit Oracle jdk 1.8 (see stacktrace)
> Reporter: Lars Borup Jensen
> Priority: Critical
>
> We've been using 3.5.2 for a longer period of time and just recently upgraded
> to 3.6.0 and then the problems started.
> First we experienced way longer build times when running the absolutely same
> build in 3.6.0 than 3.5.2. Using -B when running locally does seem to improve
> build time but still not quite the same.
> The main issue and one that is really causing us headaches is that Surefire
> 2.22.0 suddently started failing to create forks when running tests - setting
> forkCount does help on this, but then we come back to the above mentioned
> problem: build time, which then becomes painfully slow.
> So our discovery is: same source, same POM (same versions of plugins etc)
> fails to build on 3.6.0 but works on 3.5.2 (and even faster) - do you have
> any pointers for us, what to look for?
> Stacktrace from Maven
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on
> project myproj: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\projects\myproj\proj\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] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
