Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-148840605
@gliptak I had an offline discussion with @davies . Let's do the following:
1. Change L259 in `pyspark/tests.py` to:
~~~python
# Regression test
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-147903176
What is the next step on this pull request? Thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-146384917
@JoshRosen How are the doctest-s triggered on the commandline and in
Jenkins?
```
$ python/run-tests --help
No handlers could be found for logger "root"
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-146369057
@JoshRosen I do not have python2.6 installed (or available as a package)
locally
---
If your project is set up for it, you can reply to this email and have your
reply
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145966339
@gliptak, can you try to reproduce the failure locally? See
`./pyspark/run-tests --help` for hints on how to run only this test suite under
Python 2.6.
---
If your p
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145966026
I guess that this doesn't handle doctests, right? Is there any way to get
XML for those, too? If not, could you edit the PR title / description to
reflect this?
---
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145965472
Huh, looks like the last two failures were for the same PySpark test:
```
==
FAIL [0
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145685144
[Test build #43252 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43252/console)
for PR 8323 at commit
[`cd654c7`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145685213
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145685209
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145680234
[Test build #43252 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43252/consoleFull)
for PR 8323 at commit
[`cd654c7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145678696
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145678664
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 h
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-145678231
test this please
---
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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144940953
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144940955
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144940922
[Test build #43176 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43176/console)
for PR 8323 at commit
[`cd654c7`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144939063
[Test build #43176 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43176/consoleFull)
for PR 8323 at commit
[`cd654c7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144937598
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144937613
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 have
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144937221
it seems that this PR has a higher-than-normal failure rate .. I don't know
why. +@davies
---
If your project is set up for it, you can reply to this email and have you
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144937159
test this please
---
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 featur
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144553667
@mengxr Thank you for guiding this
---
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 n
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144262375
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144262351
[Test build #43113 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43113/console)
for PR 8323 at commit
[`cd654c7`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144262374
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144258982
[Test build #43113 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43113/consoleFull)
for PR 8323 at commit
[`cd654c7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144258851
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144258864
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 have
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144258490
test this please
---
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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144250376
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144250373
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144250308
[Test build #43109 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43109/console)
for PR 8323 at commit
[`cd654c7`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144242662
[Test build #43109 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43109/consoleFull)
for PR 8323 at commit
[`cd654c7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144234969
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144234750
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 h
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144232414
test this please
---
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 featur
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144231371
Though Jenkins failed, I can see the report now:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43107/testReport/junit/(root)/SerializationTestCase/tes
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144231109
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144231108
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144231086
[Test build #43107 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43107/console)
for PR 8323 at commit
[`cd654c7`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144229089
[Test build #43107 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43107/consoleFull)
for PR 8323 at commit
[`cd654c7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144229016
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144229030
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 have
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144228584
test this please
---
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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144222653
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144222623
[Test build #43104 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43104/console)
for PR 8323 at commit
[`cd654c7`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144222652
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144220623
[Test build #43104 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43104/consoleFull)
for PR 8323 at commit
[`cd654c7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144219573
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 have
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144219524
@mengxr I pushed a commit with the updated location.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144219552
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144107959
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144107963
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144107798
[Test build #43090 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43090/console)
for PR 8323 at commit
[`66bdb2b`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144102599
[Test build #43090 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43090/consoleFull)
for PR 8323 at commit
[`66bdb2b`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144101956
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 h
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143948538
@gliptak We use `**/target/test-reports/*.xml` on Jenkins to locate XML
reports. So `target/surefire-reports` may not work. (@shaneknapp please correct
me if I'm wrong.)
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143935192
i'll take a look at the config tomorrow
On Mon, Sep 28, 2015 at 6:02 PM, gliptak wrote:
>
>
https://amplab.cs.berkeley.edu/jenkins/job/NewSparkP
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143914542
https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1810/testReport/
doesn't seem to list the Python tests.
Can somebody with access t
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143912578
[Test build #1821 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1821/console)
for PR 8323 at commit
[`66bdb2b`](https://github
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143910323
[Test build #1821 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1821/consoleFull)
for PR 8323 at commit
[`66bdb2b`](https://git
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143894295
unittest-xml-reporting is installed on AMPLab Jenkins. So let's call
Jenkins again.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143894172
test this please
---
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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143158439
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143158438
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143158210
[Test build #43015 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43015/console)
for PR 8323 at commit
[`66bdb2b`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143152365
[Test build #43015 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43015/consoleFull)
for PR 8323 at commit
[`66bdb2b`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143152016
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143151996
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 h
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143151781
Created https://issues.apache.org/jira/browse/SPARK-10830.
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143151797
test this please
---
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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143089602
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143089579
[Test build #42996 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42996/console)
for PR 8323 at commit
[`66bdb2b`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143089603
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143087342
[Test build #42996 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42996/consoleFull)
for PR 8323 at commit
[`66bdb2b`](https://gith
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143087075
@mengxr Revised.
---
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 featu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143086873
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143086887
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 have
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143069705
could you create a spark issue for the plugin and assign it to me?
also, i won't be able to do this until monday, as i'm about to leave town
for the weeken
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143059734
@shaneknapp Could you take a look at this PR and see whether we can install
https://pypi.python.org/pypi/unittest-xml-reporting/1.12.0 on Jenkins?
@gliptak We sho
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143055479
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143055430
[Test build #42980 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42980/console)
for PR 8323 at commit
[`e9a711e`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143055476
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143052719
[Test build #42980 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42980/consoleFull)
for PR 8323 at commit
[`e9a711e`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143052323
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143052305
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 h
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143051862
@mengxr Thanks for the local lint pointer
---
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8323#discussion_r40292729
--- Diff: python/pyspark/streaming/tests.py ---
@@ -1297,4 +1299,5 @@ def search_kinesis_asl_assembly_jar():
for testcase in testcases:
sy
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142843121
Please fix Python style issue:
~~~
./python/pyspark/streaming/tests.py:1303:13: E128 continuation line
under-indented for visual indent
~~~
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142758037
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142757948
[Test build #42935 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42935/consoleFull)
for PR 8323 at commit
[`18f5901`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142758033
[Test build #42935 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42935/console)
for PR 8323 at commit
[`18f5901`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142758036
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142757722
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142757740
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142756653
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142756655
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142756649
[Test build #42933 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42933/console)
for PR 8323 at commit
[`05e5a37`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-142756590
[Test build #42933 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42933/consoleFull)
for PR 8323 at commit
[`05e5a37`](https://gith
1 - 100 of 131 matches
Mail list logo
