Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-219690860
Hi, All.
I'm reporting about the recent failures of Travis CI here.
Since this PR was committed a week ago, I've been monitoring Travis CI on
my
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218291417
@nchammas . I see what you mean now. For INFRA-7367 , Jenkins wanted to use
Travis CI API. Yes, it's not possible as you said. We're able to see just
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218286685
Yep. Thank you for giving test drive chance, @srowen and for understanding
that, @nchammas .
In terms of computing resources, now we can take advantage of
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218283776
@dongjoon-hyun - Here's the previous discussion:
https://issues.apache.org/jira/browse/INFRA-7367
It looks like Apache Infra has always supported posting
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218280872
Yeah I don't think this will cause Travis to post those nice build
messages. Right now it won't even email us. It does let anyone who cares go
look to see if the lint
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218280054
Hi, @nchammas . Thank you so much for fast attention!
First of all, I'm not sure about the history well. But, maybe, Apache
policy seems to be changed
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218279426
Thank you, @srowen !
---
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
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218276172
@dongjoon-hyun - What's the intended workflow here? Is the intention that
contributors will manually open Travis to check the build results? Because last
time we
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12980
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218274486
Merged in master
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218274251
OK, seems reasonable to give this a shot in master and see how it goes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218259463
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218259461
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218259198
**[Test build #58243 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58243/consoleFull)**
for PR 12980 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218229355
@srowen , I updated the comments by explaining the purpose of this test
harness clearly. I didn't described about the Jenkins-related stuff because
that's not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218227497
**[Test build #58243 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58243/consoleFull)**
for PR 12980 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12980#discussion_r62657571
--- Diff: .travis.yml ---
@@ -0,0 +1,48 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218078988
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218078986
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218078792
**[Test build #58208 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58208/consoleFull)**
for PR 12980 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218068787
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218068785
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218068656
**[Test build #58204 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58204/consoleFull)**
for PR 12980 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218062958
**[Test build #58208 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58208/consoleFull)**
for PR 12980 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218062547
@srowen
I added comments, too.
---
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
25 matches
Mail list logo
