Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6807
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111788053
Looks like R is a little different from other modules because there's no
`src/main/resources`. I added `target` in front of the path. Let's see if this
works.
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111799888
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/6807#issuecomment-111799883
[Test build #34876 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34876/console)
for PR 6807 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111788093
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111788118
[Test build #34876 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34876/consoleFull)
for PR 6807 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111788095
Merged build started.
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111859493
@andrewor14 looks like that worked ? I do see a `target/unit-tests.log` and
it contains logs from R unit tests.
---
If your project is set up for it, you can reply to
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111872417
Oh, is that what `target/unit-tests.log` is? I was expecting it to go under
`R/target/unit-tests.log`. That would be more consistent with the other modules.
---
If
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111872378
wait really? I don't:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34876/artifact/
---
If your project is set up for it, you can reply to this
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111873315
Hmm so I think for the other projects Maven probably care to go into the
directory before running tests while it doesn't happen for R. Lets see how the
latest one goes
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111879276
`R/target/unit-tests.log` exists this time. I guess this is good to merge ?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111872747
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111872734
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111879124
[Test build #34896 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34896/console)
for PR 6807 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111879137
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111906932
Yup, lgtm. Feel free to merge 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111873179
[Test build #34896 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34896/consoleFull)
for PR 6807 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111761470
yeah, it should just work
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111769401
We could try to make that `R/target/unit-tests.log` ? But I'm not sure if
log4j creates directories if they don't exist. BTW is there a jenkins config
option that
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111762562
Cool - LGTM.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111769130
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111769181
Hm, actually the R logs don't appear to be showing up
---
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/6807#issuecomment-111769125
[Test build #34854 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34854/console)
for PR 6807 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111760651
[Test build #34854 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34854/consoleFull)
for PR 6807 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111760618
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111760615
Merged build triggered.
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/6807#issuecomment-111760603
This makes sense @andrewor14 -- Does this also get put in `R/target/`
automatically ? I see `python/target` in
28 matches
Mail list logo
