[
https://issues.apache.org/jira/browse/HIVE-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brock Noland updated HIVE-4892:
-------------------------------
Description:
HIVE-4675 was merged but there are still a few minor issues we need to cleanup:
* README is out of date
* Need to limit the number of failed source directories we copy back from the
slaves
* when looking for TEST-*.xml files we look at both the log directory (good)
and the failed source directories (bad) therefore duplicating failures in
jenkins report
* We need to process bad hosts in the finally block of PTest.run
* Need a mechanism to clean the ivy and maven cache
* PTest2 fails to publish a comment to a JIRA sometimes (HIVE-4889)
was:
HIVE-4675 was merged but there are still a few minor issues we need to cleanup:
* README is out of date
* Need to limit the number of failed source directories we copy back from the
slaves
* when looking for TEST-*.xml files we look at both the log directory (good)
and the failed source directories (bad) therefore duplicating failures in
jenkins report
* We need to process bad hosts in the finally block of PTest.run
* Need a mechanism to clean the ivy and maven cache
> PTest2 cleanup after merge
> --------------------------
>
> Key: HIVE-4892
> URL: https://issues.apache.org/jira/browse/HIVE-4892
> Project: Hive
> Issue Type: Bug
> Reporter: Brock Noland
> Assignee: Brock Noland
>
> HIVE-4675 was merged but there are still a few minor issues we need to
> cleanup:
> * README is out of date
> * Need to limit the number of failed source directories we copy back from the
> slaves
> * when looking for TEST-*.xml files we look at both the log directory (good)
> and the failed source directories (bad) therefore duplicating failures in
> jenkins report
> * We need to process bad hosts in the finally block of PTest.run
> * Need a mechanism to clean the ivy and maven cache
> * PTest2 fails to publish a comment to a JIRA sometimes (HIVE-4889)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
