desaikomal opened a new pull request, #2526:
URL: https://github.com/apache/helix/pull/2526

   ### Issues
   - [x] My PR addresses the following Helix issues and references them in the 
PR description:
   Fixes 2522
   
   ### Description
   - [x] Here are some details about my PR, including screenshots of any UI 
changes:
   This test case failed just once and that too recently. We haven't changed 
any core logic in the code path of Task management.
   
   The failure happened because:
   2023-06-05T21:37:59.7170747Z [ERROR] 
testWorkflowPausedTimeout(org.apache.helix.integration.task.TestWorkflowTermination)
  Time elapsed: 10.13 s  <<< FAILURE! 2023-06-05T21:37:59.7171834Z 
org.apache.helix.HelixException: Fail to stop the workflow/queue 
testWorkflowPausedTimeout with in 10000 milliseconds.
   
   Indicating the timeout was not sufficient. So increased the timeout.
   
   
   ### Tests
   
   - [ ] The following tests are written for this issue:
   
   - The following is the result of the "mvn test" command on the appropriate 
module:
   Testing done: since this is CI failure, ran into my private branch 3/4 times 
https://github.com/desaikomal/helix/actions/workflows/Helix-PR-CI.yml
   
   
   ### Changes that Break Backward Compatibility (Optional)
   
   - My PR contains changes that break backward compatibility or previous 
assumptions for certain methods or API. They include:
   
   (Consider including all behavior changes for public methods or API. Also 
include these changes in merge description so that other developers are aware 
of these changes. This allows them to make relevant code changes in feature 
branches accounting for the new method/API behavior.)
   
   ### Documentation (Optional)
   
   - In case of new functionality, my PR adds documentation in the following 
wiki page:
   
   (Link the GitHub wiki you added)
   
   ### Commits
   
   - My commits all reference appropriate Apache Helix GitHub issues in their 
subject lines. 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
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Code Quality
   
   - My diff has been formatted using helix-style.xml 
   (helix-style-intellij.xml if IntelliJ IDE is used)
   


-- 
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.

To unsubscribe, e-mail: [email protected]

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to