{"action":"opened","issue":{"url":"https://api.github.com/repos/gradle/gradle/issues/2462","repository_url":"https://api.github.com/repos/gradle/gradle","labels_url":"https://api.github.com/repos/gradle/gradle/issues/2462/labels{/name}","comments_url":"https://api.github.com/repos/gradle/gradle/issues/2462/comments","events_url":"https://api.github.com/repos/gradle/gradle/issues/2462/events","html_url":"https://github.com/gradle/gradle/issues/2462","id":242667528,"number":2462,"title":"Improve context logging in plain console for parallel build","user":{"login":"szpak","id":148013,"avatar_url":"https://avatars2.githubusercontent.com/u/148013?v=3","gravatar_id":"","url":"https://api.github.com/users/szpak","html_url":"https://github.com/szpak","followers_url":"https://api.github.com/users/szpak/followers","following_url":"https://api.github.com/users/szpak/following{/other_user}","gists_url":"https://api.github.com/users/szpak/gists{/gist_id}","starred_url":"https://api.github.com/users/szpak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/szpak/subscriptions","organizations_url":"https://api.github.com/users/szpak/orgs","repos_url":"https://api.github.com/users/szpak/repos","events_url":"https://api.github.com/users/szpak/events{/privacy}","received_events_url":"https://api.github.com/users/szpak/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-07-13T11:17:12Z","updated_at":"2017-07-13T11:17:12Z","closed_at":null,"body":"Currently (as of 4.0.1) the logging in the plain console (CI service/dumping output to a file) with `--info` enabled doesn't provide information about context (task) on behalf which a given line is executed. It makes it really hard to determine some issues when parallel execution (for instance problems with task rebuilding with Build Cache enabled - `Appending inputPropertyHash for ...` are mixed up). It's especially painful using CI server executor with 32 vCPUs...\r\n\r\n### Expected Behavior\r\nAbility to clearly determine what task (or processing context in general) a given printed line is connected to. It could be a line prefix pointing to a task or even to a thread id or a worker number. Context switching would need to be marked in the second case to see where given thread/worked started/finished processing of a given unit of work.\r\n\r\n### Current Behavior\r\nThere is no easy way to connect a printed line to a task if parallel execution is enabled.\r\n\r\n### Your Environment\r\nGradle 4.0.1, Jenkins to execute Gradle jobs (can be anything with non interactive console)\r\n"}}
{"actor":{"display_login":"szpak"}}