Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
The reason for the update to `scala-xml_2.11-1.0.5.jar` was that once I
updated ScalaTest I got the issue from Jenkins that the dependency list
changed. That's when I was told about
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16309
You probably have a typo -- `Pkinesis-asl` instead of `-Pkinesis-asl`
locally. This error does not appear in Jenkins output. This still has the
`OutOfMemoryError` and I'm not sure why. It's coming
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #3509 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3509/testReport)**
for PR 16309 at commit
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
The tests ran locally on my laptop have finished after...`7431 s` which is
2 hours (!)
```
[error] (sql/test:test) sbt.TestsFailedException: Tests unsuccessful
[error]
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #3509 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3509/testReport)**
for PR 16309 at commit
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
@srowen Please help as I'm stuck with the `OutOfMemoryError: GC overhead
limit exceeded` error. Should Jenkins run the tests with 6g?
What's even more interesting is that the tests
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70306/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70306 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70306/testReport)**
for PR 16309 at commit
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
Rebasing with master to trigger tests on Jenkins...(hoping this time they
pass)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70306 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70306/testReport)**
for PR 16309 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16309
2G is not enough. I use 4G at least.
---
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 jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
I'm testing the changes locally with the following:
```
export SCALACTIC_FILL_FILE_PATHNAMES=yes
export SBT_OPTS="-Xmx2g -XX:ReservedCodeCacheSize=512m"
sbt
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16309
That's a simple "out of memory". Did you give SBT 4-6GB?
It's no big deal to push changes to see what Jenkins does with them if it's
getting hard to test locally. A few runs for a [WIP] PR is no
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
Hey @srowen, any idea about the following error? I'd appreciate any hints
to help me fix it.
```
[info] - can use a custom recovery mode factory (57 milliseconds)
Exception
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
Think the latest test failures are somehow related to:
```
Please set the environment variable SCALACTIC_FILL_FILE_PATHNAMES to yes at
compile time to enable this feature.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70251 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70251/testReport)**
for PR 16309 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70251/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70251 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70251/testReport)**
for PR 16309 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70250/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70250 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70250/testReport)**
for PR 16309 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70250 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70250/testReport)**
for PR 16309 at commit
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
Learnt about `./dev/test-dependencies.sh --replace-manifest` just now.
(Where's this all described?)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70249/
Test FAILed.
---
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
Just learnt about `export SPARK_TESTING=1` to avoid some test failures.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70249 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70249/testReport)**
for PR 16309 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70249 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70249/testReport)**
for PR 16309 at commit
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
Had to introduce changes to the tests given "Expired deprecations" in
[ScalaTest 3.0.0](http://www.scalatest.org/release_notes/3.0.0).
---
If your project is set up for it, you can reply to
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
Right. Testing ScalaTest 3.0.1 with the following sbt command:
```
sbt -Phadoop-2.3 -Pmesos -Pkinesis-asl -Pyarn -Phive-thriftserver -Phive
test:package
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16309
Yup, doesn't work I'm afraid:
```
sbt.ForkMain$ForkError: sbt.ForkMain$ForkError:
java.lang.IncompatibleClassChangeError: Implementing class
```
Does 1.12.6 fix it?
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70243/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70243 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70243/testReport)**
for PR 16309 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70243 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70243/testReport)**
for PR 16309 at commit
37 matches
Mail list logo
