[GRADLE-2618] Provide a way to disable STANDARD_[OUT/ERR] banner when test logging standard streams are enabled Created: 04/Jan/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.3
Fix Version/s: None

Type: New Feature
Reporter: mark petrovic Assignee: Unassigned
Resolution: Won't Fix Votes: 0


When running unit tests, one can configure test loggging to pass along messages written to stdout/stderr. When Gradle encounters these outputs, it passes them to stdout/stderr and includes a banner on the console such as

Gradle test > com.example.dpsmodel.ServerTest.testServer STANDARD_OUT
hello world

As a Gradle buildmaster and user I would like the ability to configure whether this banner appears, and if the banner is disabled, Gradle should pass the stdout/stderr output to console without indentation or other decoration.

I don't mind (yet) the banner so much, but my users consider it noisy and visually intrusive as they execute long-running integration tests that log to console. And I believe they make a fair point.

Thanks. Love Gradle, btw.

Comment by Adam Murdoch [ 16/Jan/13 ]

A better option for you might be to just use a test output listener to output exactly what you want:

test.onOutput { descriptor, event -> println event.message }
Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:26:50 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.