Skip to content

Should limit console output of unit test #3361

@biyuhao

Description

@biyuhao
  • I have searched the issues of this repository and believe that this is not a duplicate.
  • I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

  • Dubbo version: master branch
  • Operating System version: xxx
  • Java version: xxx

Steps to reproduce this issue

Travis-cli has a 4MB hard limit of log size [1].
Currently, our Travis log[2] is about 3.98MB, we are almost there.
We can reduce some trivial log in the console output, but keep a full log in the local file.

For example, test case org.apache.dubbo.rpc.validation.�ValidationTest� eats about 1.3MB in travis log. We can start from here.

[1]. https://docs.travis-ci.com/user/common-build-problems/#log-length-exceeded
[2]. https://api.travis-ci.org/v3/job/484750418/log.txt

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps?

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedEverything needs help from contributors

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions