Gradle
  1. Gradle
  2. GRADLE-1966

test.testLogging.showStandardStreams displays stderr not stdout

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Resolution: Fixed
    • Affects Version/s: 1.0-milestone-6
    • Fix Version/s: 1.1-rc-1

      Description

      The docs at http://gradle.org/releases/1.0-milestone-6/docs/dsl/org.gradle.api.tasks.testing.Test.html#org.gradle.api.tasks.testing.Test:testLogging say

      //makes the standard streams (err and out) visible at console when running tests

      but only stderr goes to the console. My test system definitely has both stdout and stderr streams hooked up because the "Standard output" and "Standard error" functions in the test reports display both stdout and stderr messages exactly as my code writes them.

      It could be that some other setting is needed to route stdout to the console when using test.testLogging.showStandardStreams, but if so then since the property name indicates "standardStream*s*", this needs to be documented much better.

        Activity

        Hide
        Blaine Simpson
        added a comment -

        If this is fixed so that test.testLogging.showStandardStreams causes all of those low-level debugging messages that always end up in test report "Standard output" logs, then please do provide a test.testLogging.showErrorStream too, because nobody is going to want to see all of that stuff (just makes it difficult to notice real problems).

        Show
        Blaine Simpson
        added a comment - If this is fixed so that test.testLogging.showStandardStreams causes all of those low-level debugging messages that always end up in test report "Standard output" logs, then please do provide a test.testLogging.showErrorStream too, because nobody is going to want to see all of that stuff (just makes it difficult to notice real problems).
        Hide
        Adam Murdoch
        added a comment -

        The test stdout was being logged at info level, which meant you needed to run with --info to see it. This has been changed so that now the test stdout is logged at lifecycle level.

        Show
        Adam Murdoch
        added a comment - The test stdout was being logged at info level, which meant you needed to run with --info to see it. This has been changed so that now the test stdout is logged at lifecycle level.

          People

          • Assignee:
            Unassigned
            Reporter:
            Blaine Simpson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: