GitHub user prabhjyotsingh opened a pull request:

    https://github.com/apache/zeppelin/pull/2433

    [ZEPPELIN-2684] Flaky Test: 
ParagraphActionsIT.testSingleDynamicFormTextInput

    ### What is this PR for?
    Raw Log - 
https://s3.amazonaws.com/archive.travis-ci.org/jobs/246113686/log.txt?X-Amz-Expires=30&X-Amz-Date=20170624T042931Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20170624/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=6ad442e67857da5228e08363229dc2a6748506c14fd3f17c2fcb8cf826ce9c64
    
    Travis seems to be failing at times with the paragraph state as Running and 
expecting Finished. I believe we can increase this MAX_PARAGRAPH_TIMEOUT_SEC to 
say 2min should solve this problem.
    
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### What is the Jira issue?
    * [ZEPPELIN-2684](https://issues.apache.org/jira/browse/ZEPPELIN-2684)
    
    ### How should this be tested?
    CI should be green for 3rd (Selenium) matrix.
    
    ### Questions:
    * Does the licenses files need update? N/A
    * Is there breaking changes for older versions? N/A
    * Does this needs documentation? N/A


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/prabhjyotsingh/zeppelin ZEPPELIN-2684

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2433.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2433
    
----
commit f0e123e3562fc5d1da946d079d7a869d3c9170bd
Author: Prabhjyot  Singh <prabhjyotsi...@gmail.com>
Date:   2017-06-24T04:49:40Z

    increase MAX_PARAGRAPH_TIMEOUT_SEC to 120

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to