[
https://issues.apache.org/jira/browse/SUREFIRE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325259#comment-16325259
]
Hudson commented on SUREFIRE-1454:
----------------------------------
ABORTED: Integrated in Jenkins build maven-surefire-dev #103 (See
[https://builds.apache.org/job/maven-surefire-dev/103/])
[SUREFIRE-1454] Speedup Standard Output if Tests (tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=a85d3276dbf6728ec855992352d613142aac41d3])
* (edit)
surefire-api/src/test/java/org/apache/maven/surefire/util/internal/StringUtilsTest.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/util/internal/StringUtils.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/booter/ForkingRunListener.java
> Speedup Standard Output if Tests
> --------------------------------
>
> Key: SUREFIRE-1454
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1454
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin, process
> forking
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Fix For: 2.21.0.Jigsaw
>
>
> Currently, surefire creates a new byte array with size of the input *3 for
> saving the unescaped input. This made surefire way slower than running a test
> directly in eclipse or with gradle, if it used standardout or error heavily.
> By using a list for saving the elements and converting them to an array
> afterwards, this problem is solved, and stdout-heavy surefire tests get
> faster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
