Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119705610
I've seen that failure randomly as well from changes that didn't change
anything remotely related. It doesn't mean that the error is *always*
spurious, but I wouldn't wo
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119712050
[Test build #1014 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1014/console)
for PR 6903 at commit
[`2b1a305`](https://github
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119873854
Spinning the wheel "fixed" 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 does not
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119893124
I think this is good to go. Any last comments anyone?
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-120375598
@dragos ah, sorry we seem to have merge conflicts now. I think we can merge
after that's resolved and re-tested.
---
If your project is set up for it, you can reply to
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-120388535
Oh, that's great...
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-120394316
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/6903#issuecomment-120403965
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/6903#issuecomment-120404657
[Test build #37034 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37034/consoleFull)
for PR 6903 at commit
[`c596c6f`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-120432410
[Test build #37034 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37034/console)
for PR 6903 at commit
[`c596c6f`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-120432502
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/6903
---
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/6903#issuecomment-115307653
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/6903#issuecomment-115307621
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 sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115307803
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ ì´ ë¤ìê³¼ ê°ì ì´ì ë¡ ì ì¡
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115307876
[Test build #35791 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35791/consoleFull)
for PR 6903 at commit
[`529293b`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115309008
[Test build #35791 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35791/console)
for PR 6903 at commit
[`529293b`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115309011
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115357990
I think @mengxr was involved in the javadoc fork.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115635411
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/6903#issuecomment-115635469
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/6903#issuecomment-115635810
[Test build #35857 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35857/consoleFull)
for PR 6903 at commit
[`10edaf9`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115674775
[Test build #35857 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35857/console)
for PR 6903 at commit
[`10edaf9`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115674917
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 dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115999679
@ScrapCodes @mateiz Anything else I can do to get this in?
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6903#discussion_r33419198
--- Diff: pom.xml ---
@@ -1227,6 +1222,7 @@
UTF-8
1024m
true
+true
--- End diff --
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6903#discussion_r33419206
--- Diff:
repl/scala-2.11/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1,88 +1,64 @@
-/* NSC -- new Scala compiler
- * Copyright 2005-
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-116203932
If it works, then I guess the only possibly controversial change is moving
to Scala 2.11.7, but that seems fairly harmless and positive, and 2.11 is not
the primary versi
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/6903#discussion_r33421311
--- Diff:
repl/scala-2.11/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1,88 +1,64 @@
-/* NSC -- new Scala compiler
- * Copyright 2005-
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/6903#discussion_r33421316
--- Diff: pom.xml ---
@@ -1227,6 +1222,7 @@
UTF-8
1024m
true
+true
--- End diff --
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-116256194
Only good things in 2.11.7: shaded jline dependency (so spark-sql is
working again) and various fixes in the REPL that made the fork unnecessary.
---
If your project is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-116258000
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/6903#issuecomment-116271284
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/6903#issuecomment-116272283
[Test build #35936 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35936/consoleFull)
for PR 6903 at commit
[`0ce67a6`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-116289161
[Test build #35936 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35936/console)
for PR 6903 at commit
[`0ce67a6`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-116289178
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 dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117063880
@srowen @ScrapCodes let's push this one over the wall. Happy to do whatever
is still needed!
---
If your project is set up for it, you can reply to this email and have y
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117069955
Are you able to run tests on scala 2.11 build locally. I am have tough time
with spurious failures. :(
---
If your project is set up for it, you can reply to this e
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117081979
There's some issues with the mima step, since it hard-codes 2.10 jars as
the previous version (when looking for binary incompatibilities).
---
If your project is set up
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117088274
You can may be do it with maven. That does not do mima checks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117113258
Hm, It seems that switching `./run-tests` to a python script removed the
ability to pass additional arguments from the outside, in particular
`-Dscala-2.11`. I can defini
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117243308
I had more luck with my branch. There is indeed a test failing in SQL,
regarding some user-defined function. However, tests in master fail much
earlier, so I couldn't get
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117438365
Yes, I am sort of clear that they are unrelated failures. About Mima checks
they should pick the right version artifact according to scala version. I did
not get a ch
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117496892
Regarding genjavadoc, see [my comment
earlier](https://github.com/apache/spark/pull/6903#issuecomment-115232045).
According to @pwendell, @mengxr could know more about it
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117951631
@ScrapCodes @dragos so is the current state that this is probably good to
go, or needs more work on genjavadoc before it will fully work for 2.11?
---
If your project is
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117959251
The only thing that needs to happen (for the Sbt build for Scala 2.11 to
work) is for someone to publish a genjavadoc for 2.11.7 (it's a compiler
plugin, therefore it's c
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117959727
Instead of breaking, let's skip the genjavadoc for scala 2.11 in SBT. I
hope that should be doable, @dragos ?
---
If your project is set up for it, you can reply to
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117976160
I'll have a look. The important part is to not remove it for 2.10
accidentally :)
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-117992688
Hm, I'd really rather not add another special case onto this crazy build.
Let's get genjavadoc sorted out. @mengxr do you know anything about that?
---
If your project i
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-118015682
This would be the change. I agree it's ugly, and couldn't factor out the
test...
```
+ // genjavadoc has not been published for 2.11.7 yet, so we skip it in
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-118312019
According to #6506 the artifact is built and published by @brkyvz. Can we
get an update?
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119162901
@brkyvz I think this is in your court -- can you help?
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119224930
@dragos @srowen Sorry I missed this thread! The official genjavadoc doesn't
support 2.11.7 yet
(https://github.com/typesafehub/genjavadoc/blob/master/project/Build.scala#
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119227844
@mengxr I think (0 to 7) is inclusive, so probably it would work. Thanks!
Looking forward to closing this one :)
---
If your project is set up for it, you can reply to t
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119240646
Hey, sorry for missing this thread. I'll publish the 2.11.7 version today
and ping you all.
---
If your project is set up for it, you can reply to this email and have yo
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119271862
@dragos Sorry I was looking at my local master. They added 2.11.7 12 days
ago:)
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119272261
@dragos Just published the genjavadoc 2.11.7!
---
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 proj
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/6903#discussion_r34064787
--- Diff:
repl/scala-2.11/src/test/scala/org/apache/spark/repl/ReplSuite.scala ---
@@ -22,14 +22,11 @@ import java.net.URLClassLoader
import scala.c
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119500955
Thanks @brkyvz. In principle there's nothing I need to do for this PR
(except the whitespace changes you pointed out), but I'll run tests locally
again.
**Could
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119530772
[Test build #1006 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1006/consoleFull)
for PR 6903 at commit
[`0ce67a6`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119550063
[Test build #1006 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1006/console)
for PR 6903 at commit
[`0ce67a6`](https://github
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119556023
I removed spaces around imports (can't this be checked by ScalaStyle?).
I noticed a few tests are looping on 2.11 (both on 2.11.6 and 2.11.7). I'll
investigate th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119556562
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119558510
Yes, it can be. But enforcing it codebase wide is huge(+ unjustified, in
the sense it affect code history) effort.
See :
https://github.com/scalastyle/scalastyle
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119571715
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/6903#issuecomment-119572104
[Test build #1008 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1008/consoleFull)
for PR 6903 at commit
[`0ce67a6`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119573238
[Test build #1008 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1008/console)
for PR 6903 at commit
[`0ce67a6`](https://github
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119573371
[Test build #36793 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36793/consoleFull)
for PR 6903 at commit
[`2b1a305`](https://gith
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119580636
I think this is a legit failure?
```
Scalastyle checks failed at following occurrences:
[error] sbt.IncompatiblePluginsException: Binary incompatibility in
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119581892
Looks like that... I have no idea what it means though. I'll have a look
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119617418
I can't reproduce it. How did you run it?
```
$ dev/lint-scala
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=512m; support was
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119617730
[Test build #36793 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36793/console)
for PR 6903 at commit
[`2b1a305`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119617854
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119622348
Have a look at
http://stackoverflow.com/questions/22628547/binary-incompatibility-in-plugins-detected-in-play-2-1-3-project-after-upgrading
which makes me think this is s
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119631126
But the latest Jenkins build succeeded (at least, style checks did). Now it
fails a test in catalyst. So this is a spurious error, it seems?
Note that there is no
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119631987
[Test build #1012 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1012/consoleFull)
for PR 6903 at commit
[`2b1a305`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119673909
[Test build #1012 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1012/console)
for PR 6903 at commit
[`2b1a305`](https://github
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119676911
Yeah these are different failures each time. I'm not sure what's going on
-- still am not sure why these changes would make things merely _flakier_. Let
me spin the wheel
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-119677325
[Test build #1014 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1014/consoleFull)
for PR 6903 at commit
[`2b1a305`](https://git
79 matches
Mail list logo
