[GRADLE-3000] logging.captureStandardOutput does not capture all stdout when running in parallel Created: 21/Jan/14 Updated: 06/Feb/17 Resolved: 06/Feb/17
I have encountered a problem with captureStandardOutput when running several projects in parallel.
The problem is that although I have set logging to capture stdout to log level INFO I get output (on the default lifecycle level) from some sub-projects, but not all. The number of projects emitting the task output is dependent of the number of parallel threads.
In my small setup described below I have four sub-projects besides the root project.
This can be easily reproduced by creating a small build.gradle file with this:
and a settings.gradle:
include "sub1", "sub2", "sub3", "sub4"
and the empty folders "sub1", "sub2", "sub3", "sub4"
$ ./gradlew --parallel-threads=4
$ ./gradlew --parallel-threads=6
$ ./gradlew --parallel-threads=7
I have run this on macos 10.9.1
|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:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Chuck May [ 15/Nov/16 ]|
This is still a bug and I would love if this could be looked at. Our parallel build logs are close to unusable because of all the logging noise. Only affects parallel builds.
|Comment by Benjamin Muschko [ 06/Feb/17 ]|
We are aware of the issue and are currently working on improved console output. For more details please see: https://github.com/gradle/gradle/blob/master/design-docs/improved-console.md. Each of the stories in the spec is represented as a Gradle issue on https://github.com/gradle/gradle-private/issues/456. I propose you follow the work that is currently in flight and open an issue after releasing a significant milestone thereafter if needed.