Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9030#issuecomment-146680712
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9019#discussion_r41566709
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -75,6 +76,242 @@ trait ScalaReflection {
*/
pri
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9019#discussion_r41566743
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -75,6 +76,242 @@ trait ScalaReflection {
*/
pri
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9032#issuecomment-146681215
[Test build #43423 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43423/consoleFull)
for PR 9032 at commit
[`fed0b98`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9034#issuecomment-146681399
[Test build #43424 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43424/consoleFull)
for PR 9034 at commit
[`73c7048`](https://gith
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9034
---
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 enab
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/9029#issuecomment-146681852
@mfliu I think thats just a flaky test, but irrespective of that your
changes should be against the current `master` branch. Right now it looks like
there are a lot mor
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146681921
The last build failure was caused by #8983, which broke master and has just
been reverted.
---
If your project is set up for it, you can reply to this email and have
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146681939
retest 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 f
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/8983#issuecomment-146682265
@marmbrus .. sorry about it. Is there a way i can look at the list of
failures ?
I had run :
build/mvn -Pyarn -Phadoop-2.6 -Phive -Phive-thriftserver
-Dhadoo
GitHub user tgravescs opened a pull request:
https://github.com/apache/spark/pull/9035
[SPARK-10858] YARN: archives/jar/files rename with # doesn't work unl
https://issues.apache.org/jira/browse/SPARK-10858
The issue here is that in resolveURI we default to calling new
File
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9019#discussion_r41567674
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -75,6 +76,242 @@ trait ScalaReflection {
*/
pri
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8983#issuecomment-146682761
just reopen this PR and we will trigger a test on our jenkin for it.
For local test, you can do `./build/sbt catalyst/test`
---
If your project is set up for
Github user adrian555 commented on the pull request:
https://github.com/apache/spark/pull/9031#issuecomment-146682793
Tests 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 does not have this featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9035#issuecomment-146682883
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/9016#issuecomment-146682889
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/8988#issuecomment-146682895
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/9035#issuecomment-146682906
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/8909#issuecomment-146682900
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/9016#issuecomment-146682930
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/8988#issuecomment-146682933
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/8909#issuecomment-146682934
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146683177
[Test build #43427 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43427/consoleFull)
for PR 8988 at commit
[`fb6ee9f`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8909#issuecomment-146683288
[Test build #43428 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43428/consoleFull)
for PR 8909 at commit
[`ab5e46c`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9016#issuecomment-146683593
[Test build #43426 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43426/consoleFull)
for PR 9016 at commit
[`06161e3`](https://gith
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9035#issuecomment-146683862
Pretty sure this is right, yeah
---
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/9016#issuecomment-146683971
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/9016#issuecomment-146683991
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9019#discussion_r41568528
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -75,6 +76,242 @@ trait ScalaReflection {
*/
pri
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9000#discussion_r41568609
--- Diff: core/src/main/scala/org/apache/spark/storage/MemoryStore.scala ---
@@ -489,17 +478,21 @@ private[spark] class MemoryStore(blockManager:
BlockManag
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9019#discussion_r41568645
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/objects.scala
---
@@ -0,0 +1,334 @@
+/*
+ * Licensed to the Apache Soft
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9035#issuecomment-146684626
[Test build #43425 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43425/consoleFull)
for PR 9035 at commit
[`4cd8912`](https://gith
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9000#discussion_r41568778
--- Diff: core/src/main/scala/org/apache/spark/storage/MemoryStore.scala ---
@@ -507,16 +500,17 @@ private[spark] class MemoryStore(blockManager:
BlockManag
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9019#issuecomment-146685224
Overall looks good! Left a few clarification questions.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/8983#issuecomment-146685208
@cloud-fan
I didn't see a re-open option on this pull request. Do i have to create a
new pull request ?
Please let me know ..
---
If your project is set up
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9000#discussion_r41569134
--- Diff: core/src/main/scala/org/apache/spark/storage/MemoryStore.scala ---
@@ -507,16 +500,17 @@ private[spark] class MemoryStore(blockManager:
BlockManag
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9016#discussion_r41569273
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/columnar/ColumnType.scala ---
@@ -324,15 +296,18 @@ private[sql] object STRING extends
NativeColumnT
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146685643
A note about interoperability:
Hive 1.2.1 can read Parquet arrays and maps written in standard format.
However, it still doesn't recognize Parquet decimals sto
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9000#discussion_r41569345
--- Diff: core/src/main/scala/org/apache/spark/storage/MemoryStore.scala ---
@@ -525,22 +519,40 @@ private[spark] class MemoryStore(blockManager:
BlockManag
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9000#discussion_r41569596
--- Diff: core/src/main/scala/org/apache/spark/storage/MemoryStore.scala ---
@@ -507,16 +500,17 @@ private[spark] class MemoryStore(blockManager:
BlockManag
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9016#issuecomment-146686989
[Test build #43429 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43429/consoleFull)
for PR 9016 at commit
[`23e127c`](https://gith
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8983#issuecomment-146688197
open a new one is also OK.
---
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 hav
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9000#discussion_r41570238
--- Diff: core/src/main/scala/org/apache/spark/storage/MemoryStore.scala ---
@@ -525,22 +519,40 @@ private[spark] class MemoryStore(blockManager:
BlockManag
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9015#discussion_r41570443
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/TungstenAggregationIterator.scala
---
@@ -280,17 +286,25 @@ class TungstenAggregatio
Github user zero323 commented on the pull request:
https://github.com/apache/spark/pull/9009#issuecomment-146689536
@jkbradley Done.
---
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9016#discussion_r41570679
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/columnar/ColumnType.scala ---
@@ -324,15 +296,18 @@ private[sql] object STRING extends
NativeColumnType
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9015#discussion_r41571056
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/utils.scala ---
@@ -204,10 +144,13 @@ object Utils {
}
def planAg
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9019#issuecomment-146690958
Since this is the infrastructural work of encoder/decoder, let's merge this
and use a follow-up pr to address the comments. So, other people can start to
play with it.
-
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9019
---
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 enab
GitHub user dilipbiswal opened a pull request:
https://github.com/apache/spark/pull/9036
[SPARK-8654] [SQL] Analysis exception when using NULL IN (...) : invalid
cast
In the analysis phase , while processing the rules for IN predicate, we
compare the in-list types to the lhs exp
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146691810
ok to test
---
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
en
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146691882
Since we already have an option for being compatible with Hive (the legacy
mode), then we should not worry that (do not need to change anything in this
PR).
Hive
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146691960
Can one of the admins verify this patch?
---
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 pr
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9033#issuecomment-146692696
Jenkins, OK to test
---
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 fea
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146692581
@cloud-fan
Hi Wenchen, Can you please review the update to the test case ? Thank you.
---
If your project is set up for it, you can reply to this email and have
Github user rgbkrk commented on the pull request:
https://github.com/apache/spark/pull/8318#issuecomment-146693064
Looks like @alope107 added fixes for the last few reviews. How does this
stand now?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user olarayej commented on the pull request:
https://github.com/apache/spark/pull/8984#issuecomment-146693478
@shivaram Could you share the best practices to merge the changes from the
master branch into the PR branch? This looks like a very common thing and the
team (@NarineK,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9030#issuecomment-146693557
[Test build #1861 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1861/console)
for PR 9030 at commit
[`9b79e6f`](https://github
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146693831
ok to test
---
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
e
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/8318#discussion_r41572924
--- Diff: python/pyspark/__init__.py ---
@@ -36,6 +36,31 @@
Finer-grained cache persistence levels.
"""
+import os
+import sys
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146693992
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146694130
[Test build #43430 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43430/consoleFull)
for PR 9036 at commit
[`a1ee629`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146694010
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/9036#issuecomment-146694616
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/9036#issuecomment-146694612
[Test build #43430 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43430/console)
for PR 9036 at commit
[`a1ee629`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146694615
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8984#issuecomment-146695587
There are a number of ways to do this, so this is just the way I do it
personally. In my case I have two remotes in my git setup. So my .git/config
looks something like
Github user rerngvit commented on the pull request:
https://github.com/apache/spark/pull/8962#issuecomment-146695490
The errors seem not related to the PR. There might be an issue with Jenkins.
"ERROR: Timeout after 15 minutes
ERROR: Error fetching remote repo 'origin'"
---
If
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/9008#discussion_r41573997
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tree/impl/RandomForest.scala ---
@@ -1211,4 +1212,34 @@ private[ml] object RandomForest extends Logging {
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8962#issuecomment-146695915
Jenkins, retest 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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8962#issuecomment-146696093
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/8962#issuecomment-146696116
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9015#discussion_r41574147
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/utils.scala ---
@@ -204,10 +144,13 @@ object Utils {
}
def planAg
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9015#issuecomment-146696229
LGTM. Merging to 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 dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146696603
@cloud-fan , hi, how do we trigger a retest ?
---
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/8962#issuecomment-146697127
[Test build #43431 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43431/consoleFull)
for PR 8962 at commit
[`1339e24`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146697687
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9015
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146697635
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 davies commented on the pull request:
https://github.com/apache/spark/pull/8909#issuecomment-146699044
@marmbrus @yhuai @andrewor14 I should have addressed all of your comments
(except lack of more docs), could you take another pass? The failed test is not
related to this.
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/6648#discussion_r41575081
--- Diff:
network/shuffle/src/main/java/org/apache/spark/network/shuffle/ExternalShuffleBlockResolver.java
---
@@ -163,12 +163,12 @@ public void registerExecu
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9000#discussion_r41575231
--- Diff: core/src/main/scala/org/apache/spark/storage/MemoryStore.scala ---
@@ -525,22 +519,40 @@ private[spark] class MemoryStore(blockManager:
BlockManag
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/6648#discussion_r41575239
--- Diff:
core/src/main/java/org/apache/spark/shuffle/unsafe/UnsafeShuffleWriter.java ---
@@ -125,6 +129,7 @@ public UnsafeShuffleWriter(
taskContext
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-14671
@davies Although Hive doesn't write using standard Parquet format, it can
read standard LIST and MAP. It just doesn't recognize compact decimals. So even
if we turn of
GitHub user holdenk opened a pull request:
https://github.com/apache/spark/pull/9037
[SPARK-10991][ML] logistic regression training summary handle empty
prediction col
LogisticRegression training summary should still function if the
predictionCol is set to an empty string or otherw
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9037#issuecomment-146701173
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/9036#issuecomment-146701214
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/9037#issuecomment-146701153
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/9036#issuecomment-146701216
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/8962#issuecomment-146701289
[Test build #43431 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43431/console)
for PR 8962 at commit
[`1339e24`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8962#issuecomment-146701389
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/8962#issuecomment-146701388
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9030#issuecomment-146701450
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 feature
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9037#issuecomment-146701665
[Test build #43433 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43433/consoleFull)
for PR 9037 at commit
[`b9cb751`](https://gith
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-146701712
@cloud-fan
It seems to fail now with the following exception ..
hudson.plugins.git.GitException: Failed to fetch from
https://github.com/apache/spark.git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9030#issuecomment-146701970
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/9037#issuecomment-146702024
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/9037#issuecomment-146702021
[Test build #43433 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43433/console)
for PR 9037 at commit
[`b9cb751`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9037#issuecomment-146702025
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/9030#issuecomment-146701946
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
401 - 500 of 878 matches
Mail list logo
