sv2000 opened a new pull request #3123:
URL: https://github.com/apache/incubator-gobblin/pull/3123


   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I 
have checked off all the steps below!
   
   
   ### JIRA
   - [x] My PR addresses the following [Gobblin 
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references 
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1284
   
   
   ### Description
   - [x] Here are some details about my PR, including screenshots (if 
applicable):
   On local build, we see intermittent failures in the following test classes:
   
   RateControlledFileSystemTest
   HiveSourceTest
   HighLevelConsumerTest
   The test failures happen due to a combination of reasons:
   
   Failure to clean up files/directories (HiveSourceTest)
   Inadequate number of iterations resulting in sample mean not converging 
(RateControlledFileSystemTest), and
   Timeout exceptions (HighLevelConsumerTest)
   This task attempts to fix the flakiness in these test classes.
   
   The build.gradle has been modified to add gpg to rat exclusion.
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   
   
   ### Commits
   - [x] My commits all reference JIRA issues in their subject lines, and I 
have squashed multiple commits if they address the same issue. In addition, my 
commits follow the guidelines from "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to