[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
GitHub user bzz opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/810

    ZEPPELIN-783 fix CI failure on Spark download

    ### What is this PR for?
    Improves CI by hard-ending spark download failures that are responsible for recent CI red on `master`
   
    ### What type of PR is it?
    Bug Fix | Hot Fix
   
    ### Todos
   
    ### What is the Jira issue?
    [ZEPPELIN-783](https://issues.apache.org/jira/browse/ZEPPELIN-783)
   
    ### How should this be tested?
    CI must be green
   
    ### 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/bzz/incubator-zeppelin ZEPPELIN-783-fix-ci-spark-download

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

    https://github.com/apache/incubator-zeppelin/pull/810.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 #810
   
----
commit 346e07588671684f8343a28b881c12889865dc61
Author: Alexander Bezzubov <[hidden email]>
Date:   2016-04-01T03:04:06Z

    ZEPPELIN-783: upd shell style

commit b413743148072df862009300fb6ec8b0a8433d40
Author: Alexander Bezzubov <[hidden email]>
Date:   2016-04-01T03:15:43Z

    ZEPPELIN-783: refactoring - extract SPARK_ARCHIVE var

commit bd1d5e22fb0d76360dd924bf0726910a0ae8ed63
Author: Alexander Bezzubov <[hidden email]>
Date:   2016-04-01T03:17:48Z

    ZEPPELIN-783: add cleanup on download failure

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
Github user bzz commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-204388627
 
    Ready to be merged \cc @felixcheung @jongyoul @Leemoonsoo for a review


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user echarles commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-204409082
 
    That's a nice improvement which will remove some failures, but download failures also occur on simple jars (writing this down while thinking to those erratic failures).


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user bzz commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-204424456
 
    @echarles So true. I plan to take care of that as a next step under a separate PR, after dealing with Spark downloads here first.


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user felixcheung commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-204571013
 
    Right, dependencies download is another frequent source of download timeout issues. Added a comment on that.



---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user bzz commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-204659044
 
    @felixcheung feedback addressed in 039513b


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user bzz commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-204668582
 
    Merging, as this is a hotfix and there is no more discussion


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-zeppelin/pull/810


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user bzz commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-204675812
 
    [ZEPPELIN-786](https://issues.apache.org/jira/browse/ZEPPELIN-786) was created for caching `.m2`
   
    Looks like current CI on master is failing to populate cache and download 1.1 and 1.2 from slow mirrors..


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user felixcheung commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-204763645
 
    yea, unfortunately it seems some of the apache mirrors are very slow..


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user bzz commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-205158934
 
    After at least 2 more PRs failed on downloading Spark distr again I have re-open [ZEPPELIN-783](https://issues.apache.org/jira/browse/ZEPPELIN-783) and thinking about increasing a default 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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-zeppelin pull request: ZEPPELIN-783 fix CI failure on Sp...

yx91490
In reply to this post by yx91490
Github user felixcheung commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/810#issuecomment-205284680
 
    This indicates a corrupted file (which seems fairly common) so would not seem to be download timeout related:
   
    https://s3.amazonaws.com/archive.travis-ci.org/jobs/120500704/log.txt
   
     


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---