You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zeppelin.apache.org by Leemoonsoo <gi...@git.apache.org> on 2017/01/20 21:14:10 UTC

[GitHub] zeppelin pull request #1919: Increase WelcomePageSuite timeout

GitHub user Leemoonsoo opened a pull request:

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

    Increase WelcomePageSuite timeout

    ### What is this PR for?
    Try fix problem described in https://issues.apache.org/jira/browse/ZEPPELIN-1986.
    Almost all recent build has this failure on CI build.
    
    
    ### What type of PR is it?
    Hot Fix
    
    ### Todos
    * [x] - Increase timeout
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1986
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? no


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

    $ git pull https://github.com/Leemoonsoo/zeppelin ZEPPELIN-1986-fix

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

    https://github.com/apache/zeppelin/pull/1919.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 #1919
    
----
commit 21e6840537766c042a44c132d682a9ec0c28c5dd
Author: Lee moon soo <mo...@apache.org>
Date:   2017-01-20T21:12:09Z

    Increase WelcomePageSuite timeout

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1919: [ZEPPELIN-1986] Fix flaky test: Increase WelcomePageSu...

Posted by jongyoul <gi...@git.apache.org>.

Github user jongyoul commented on the issue:

    https://github.com/apache/zeppelin/pull/1919
  
    @Leemoonsoo Actually, in this case, I also don't have any better idea than what you do :-) Just worried about becoming more rare flaky test.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1919: [ZEPPELIN-1986] Fix flaky test: Increase Welcom...

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1919: [ZEPPELIN-1986] Fix flaky test: Increase WelcomePageSu...

Posted by jongyoul <gi...@git.apache.org>.

Github user jongyoul commented on the issue:

    https://github.com/apache/zeppelin/pull/1919
  
    @Leemoonsoo I think to prolong timeout would be realistic solution but same error may occurs when travis is under resources starvation. Can we handle it? 


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1919: [ZEPPELIN-1986] Fix flaky test: Increase WelcomePageSu...

Posted by Leemoonsoo <gi...@git.apache.org>.

Github user Leemoonsoo commented on the issue:

    https://github.com/apache/zeppelin/pull/1919
  
    @jongyoul I don't have any good idea except for change test to use less resources when travis is under resource starvation. Do you have any good idea?


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---