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

Hive QA commented on HIVE-20855:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12946606/HIVE-20855.1.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/14705/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14705/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14705/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12946606/HIVE-20855.1.patch 
was found in seen patch url's cache and a test was probably run already on it. 
Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12946606 - PreCommit-HIVE-Build

> Clean up checkstyle & other warnings for CachedStore
> ----------------------------------------------------
>
>                 Key: HIVE-20855
>                 URL: https://issues.apache.org/jira/browse/HIVE-20855
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Lars Francke
>            Assignee: Lars Francke
>            Priority: Minor
>         Attachments: HIVE-20855.1.patch
>
>
> While documenting the CachedStore in the Wiki I found a bunch of warnings, 
> inconsistencies etc. in CachedStore, RawStore and a few other related classes.
> This is a patch that cleans them up. It's almost whitespace-only.
> It does not contain semantic code changes, it does contain two or three 
> deprecations in favor of renamed methods or fields.
> This is going to be boring to review so according to the bylaws I'll ask for 
> feedback on the mailing list and will commit after a week or so.



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

Reply via email to