[
https://issues.apache.org/jira/browse/TEZ-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791435#comment-14791435
]
TezQA commented on TEZ-2836:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12756368/TEZ-2836.1.txt
against master revision 1a065b9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1145//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1145//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1145//console
This message is automatically generated.
> Avoid setting framework/system counters for tasks running in threads
> --------------------------------------------------------------------
>
> Key: TEZ-2836
> URL: https://issues.apache.org/jira/browse/TEZ-2836
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: TEZ-2836.1.txt
>
>
> Counters like FileSystemCounters, GC_TIME, CPU_TIME etc - are computed
> incorrectly in case of LocalMode, Uber, TestService and others where tasks
> may execute in threads. (The values end up being a combination of what's
> running in the process - which could be other tasks or the AM).
> It's better not to set them for now, instead of reporting incorrect values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
