[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user dongjoon-hyun commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193731456 Thank you for merging. --- 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 ha

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/11567 --- 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 ena

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user srowen commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193709656 Merged to master. Thanks all, and sorry about that. I am not sure why the PR builder passed. --- If your project is set up for it, you can reply to this email and have

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193708863 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193708860 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 projec

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193708216 **[Test build #52648 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52648/consoleFull)** for PR 11567 at commit [`fbac4a1`](https://g

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user dongjoon-hyun commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193669049 About `?s part`, @zsxwing gave us some note and pointer in #11438 . > FYI because mvn checkstyle:check depends on mvn install which cost huge time for sb

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user srowen commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193663305 Ah, OK I see now: - `scalastyle` config's location was referenced incorrectly. This was a change I should have backed out. I'm not sure why it passed the pull re

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user dongjoon-hyun commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193660852 Thank you, @srowen . The pom.xml file is updated as you said. --- If your project is set up for it, you can reply to this email and have your reply appear on GitH

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user srowen commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193660274 The file needs to be moved up a level. I'm back online in 15 mins and can take a full look at what happened there. --- If your project is set up for it, you can reply

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user srowen commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193659536 Ack, hm, that change should not have been in there. I don't know how it passed though. Yes this should be the right change because this file was not moved in the end.

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193658329 **[Test build #52648 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52648/consoleFull)** for PR 11567 at commit [`fbac4a1`](https://gi

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193657238 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 projec

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193657240 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193657236 **[Test build #52647 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52647/consoleFull)** for PR 11567 at commit [`775fbdd`](https://g

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193657119 **[Test build #52647 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52647/consoleFull)** for PR 11567 at commit [`775fbdd`](https://gi

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user rxin commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193656340 Yes please do that too. Thanks. On Tuesday, March 8, 2016, Dongjoon Hyun wrote: > Hi, @srowen and @rxin >

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user dongjoon-hyun commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193656403 Thank you! I see. --- 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 th

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user dongjoon-hyun commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193655686 Hi, @srowen and @rxin . In the dev mailing list, there is another report about the location of `scalastyle-config.xml`. In `pom.xml`, ``` dev

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193613491 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 projec

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193613494 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193612972 **[Test build #52627 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52627/consoleFull)** for PR 11567 at commit [`4a58fba`](https://g

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user dongjoon-hyun commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193578502 `PySpark` failure is irrelevant for this PR, but I rebased this PR to the master because this is still a problem. --- If your project is set up for it, you can r

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193578669 **[Test build #52627 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52627/consoleFull)** for PR 11567 at commit [`4a58fba`](https://gi

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-19389 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 projec

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-19395 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193555142 **[Test build #52614 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52614/consoleFull)** for PR 11567 at commit [`380ceb3`](https://g

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user dongjoon-hyun commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193522841 Could you review this please? @srowen and @rxin . --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as we

[GitHub] spark pull request: [HOT-FIX][BUILD] Use the new location of `chec...

Github user dongjoon-hyun commented on the pull request: https://github.com/apache/spark/pull/11567#issuecomment-193522667 Currently, Jenkins does not run `lint-java`. So this failure is not caught before. --- If your project is set up for it, you can reply to this email and have