You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/12/16 17:37:00 UTC

[jira] [Commented] (SUREFIRE-1454) Speedup Standard Output if Tests

    [ https://issues.apache.org/jira/browse/SUREFIRE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293883#comment-16293883 ] 

ASF GitHub Bot commented on SUREFIRE-1454:
------------------------------------------

Github user Tibor17 commented on the issue:

    https://github.com/apache/maven-surefire/pull/167
  
    @DaGeRe 
    Close this PR on GitHub. I have made a fix.
    See this Jira issue: https://issues.apache.org/jira/browse/SUREFIRE-1454


> 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)