[ 
https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542285#comment-16542285
 ] 

TezQA commented on TEZ-3866:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12931385/TEZ-3866.2.patch
  against master revision 4496f66.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 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:green}+1 findbugs{color}.  The patch does not introduce any 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:red}-1 core tests{color}.  The patch failed these unit tests in :
                   org.apache.tez.dag.app.TestSpeculation

Test results: 
https://builds.apache.org/job/PreCommit-TEZ-Build/2861//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2861//console

This message is automatically generated.


> add ability to pass information between plugins
> -----------------------------------------------
>
>                 Key: TEZ-3866
>                 URL: https://issues.apache.org/jira/browse/TEZ-3866
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Jaume M
>            Priority: Major
>         Attachments: TEZ-3866.1.patch, TEZ-3866.2.patch
>
>
> Distinct from TEZ-3815, since even with a hack that makes plugins aware of 
> each other, they cannot store task-specific info without calling into each 
> others' per-task structures.
> In particular, I need a piece of info that is generated when the custom 
> scheduler calls getContext().taskAllocated, to be propagated to communicator 
> plugin registerRunningTaskAttempt, so that the custom communicator could 
> include additional info in task submission (e.g. a scheduler-specific 
> priority or other instructions). There doesn't seem to be any means to do it 
> now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to