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

Hadoop QA commented on PHOENIX-5286:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12970967/PHOENIX-5286.4.x-cdh5.15.v2.patch
  against master branch at commit 27bc7140de826929fdad4c4027b609dc20b0dbe3.
  ATTACHMENT ID: 12970967

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

    {color:green}+0 tests included{color}.  The patch appears to be a 
documentation, build,
                        or dev patch that doesn't require tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2629//console

This message is automatically generated.

> IndexScrutinyToolIT Ignored in 4.x-CDH
> --------------------------------------
>
>                 Key: PHOENIX-5286
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5286
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.13.2-cdh
>            Reporter: William Shen
>            Assignee: William Shen
>            Priority: Major
>         Attachments: PHOENIX-5286.4.x-cdh5.15.v1.patch, 
> PHOENIX-5286.4.x-cdh5.15.v2.patch
>
>
> The entire {{IndexScrutinyToolIT}} is marked with {{@ignored}} in 4.x-CDH, 
> but based on James' [comment| 
> https://issues.apache.org/jira/browse/PHOENIX-4372?focusedCommentId=16258577&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16258577],
>  it seems like we should've only marked {{testOutputInvalidRowsToFile}} as 
> {{@ignored}}.
> PHOENIX-4388 is open to fix testOutputInvalidRowsToFile, but maybe we should 
> re-enable the other test cases in {{IndexScrutinyToolIT}} to make sure they 
> continue to pass with the releases.



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

Reply via email to