Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218038498
Travic CI was finished with JDK7 (30min) and JDK8 (31min) in parallel.
https://travis-ci.org/dongjoon-hyun/spark/builds/129008329
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218030211
**[Test build #58190 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58190/consoleFull)**
for PR 12980 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-218029962
Hi, @zsxwing .
According to your advice, I updated the PR; run `lint-java` after `mvn
install`. Thank you for advice!
---
If your project is set up for it,
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217958114
You're right. I maybe didn't remember the exact phrase I've read before.
By the way, 'this wastes a lot time for sbt building' is effectively different
from
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217932374
A solution is always running `mvn install` before `mvn checkstyle`.
However, this wastes a lot time for sbt build.
---
If your project is set up for it, you can reply
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217932005
> Currently, Java Linter is disabled due to lack of testing resources.
FYI. This is not correct. The problem is `mvn checkstyle` requires that the
artifacts
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217908555
Yeah but the Jenkins builds already have to download all that stuff to run
everything else like the main build right? the additional cost of running
lint-java is small?
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217908304
Yep, I did the same question before.
The answer was Jenkins also do the clean build as you mentioned for Travis
CI. In other words, in AMP cluster, there
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217805705
I don't think it's a bad thing to have some kind of Travis build running in
parallel as long as people understand what it is. Maybe some extra comments in
the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217749784
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217749785
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217749731
**[Test build #58110 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58110/consoleFull)**
for PR 12980 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217744521
Hi, @srowen . I added `test-compile`, too. You can see the result here.
https://travis-ci.org/dongjoon-hyun/spark/builds/128708372
For your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217744182
**[Test build #58110 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58110/consoleFull)**
for PR 12980 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217736741
Thank you for review, @srowen .
I'm not sure the root cause of that. According to the github log, it was
created, [disabled
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217702414
I don't think this hurts, except that it adds yet another place to look for
test results. (PS you want to add "test-compile" as a target too). What is the
reason it's
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217690316
Definitely, the failure is not related to this PR since this PR just adds
`.travis.yml` file.
```
[error] (mllib/test:test) sbt.TestsFailedException:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217689272
Merged build finished. Test FAILed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217689275
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217689064
**[Test build #58080 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58080/consoleFull)**
for PR 12980 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217683635
Hi, @rxin and @andrewor14 .
I think this is the only way to re-enable Java linter.
---
If your project is set up for it, you can reply to this email and have
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217683609
Travis CI passed. It took less than 25 minutes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217682754
**[Test build #58080 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58080/consoleFull)**
for PR 12980 at commit
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/12980
[SPARK-15207][BUILD] Use Travis CI for Java/Scala/Python Linter and JDK7/8
compilation test
## What changes were proposed in this pull request?
Currently, Java Linter is disabled
24 matches
Mail list logo
