[jira] [Commented] (CASSANDRA-15014) Unit tests failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776882#comment-16776882
]
Alex Petrov commented on CASSANDRA-15014:
-
Thank you for the review! Fixed tests not showing up, example failure:
[here|https://circleci.com/gh/ifesdjeen/cassandra/1366#tests/containers/2].
Committed to
[2.2|https://github.com/apache/cassandra/commit/a7d8ba7b10a441f9710724e65a939a46add0ae78]
and merged up to
[3.0|https://github.com/apache/cassandra/commit/b27cc37abdef959c599440edc9fb85e0bc567249],
[3.11|https://github.com/apache/cassandra/commit/7b462ec46753943281b3b4d4b106bcc4625bfae7]
and
[trunk|https://github.com/apache/cassandra/commit/5c4c75cac70dfb885a9905b7fc33a910f83ac989].
> Unit tests failure on trunk
> ---
>
> Key: CASSANDRA-15014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15014
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Dinesh Joshi
>Assignee: Alex Petrov
>Priority: Major
> Attachments: Screen Shot 2019-02-11 at 12.30.19.png, Screen Shot
> 2019-02-13 at 15.46.28.png, threads_stuck_waiting.png
>
>
> Currently org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> is failing on trunk with the following error -
> {code:java}
> [junit-timeout] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Exception in thread "main" java.lang.OutOfMemoryError:
> Metaspace
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest Tests run:
> 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest:readWithSchemaDisagreement:
> Caused an ERROR
> [junit-timeout] Forked Java VM exited abnormally. Please note the time in the
> report does not reflect the time until the VM exit.
> [junit-timeout] junit.framework.AssertionFailedError: Forked Java VM exited
> abnormally. Please note the time in the report does not reflect the time
> until the VM exit.
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.lang.Thread.run(Thread.java:748)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Test
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest FAILED
> (crashed)
> [junitreport] Processing /tmp/cassandra/build/test/TESTS-TestSuites.xml to
> /tmp/null1041131060
> [junitreport] Loading stylesheet
> jar:file:/usr/share/ant/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
> [junitreport] Transform time: 277ms
> [junitreport] Deleting: /tmp/null1041131060{code}
> I have noticed sporadic failures in the
> org.apache.cassandra.distributed.test.* suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15014) Unit tests failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776581#comment-16776581
]
Joseph Lynch commented on CASSANDRA-15014:
--
Alright, finally figured out why attaching a debugger was causing the tests to
crash, looks like the {{InstanceClassLoader}} switched from a blacklist to a
whitelist where we only use the shared class loader for whitelisted classes, I
just added a whitelist for "com.yourkit" and I was able to attach again.
Just a few comments, fix'n'ship.
* I don't think right now if a jvm-dtest fails the build actually fails (I
inserted an exception into one of the tests and {{ant test-jvm-dtest}} still
passed). Perhaps we need {{#!/bin/bash}} and {{set -e}} at the top of the file
written by {{TestLocator.java}} and {{failonerror}} set on the ant {{exec}}
line.
* Do you find that
[setting|https://github.com/apache/cassandra/compare/trunk...ifesdjeen:CASSANDRA-15014-trunk#diff-2cccd7bf48b7a9cc113ff564acd802a8R1340]
{{MetaspaceSize}} or {{MaxMetaspaceExpansion}} does anything? In my experience
they just cause a metaspace OOM before the GC can collect classes. Let's leave
them out if we don't find they help?
* After you applied my patch now there is a test-jvm-dtest and a
test-distributed target. They do different things so maybe we should have both,
but should we unify the names e.g. "test-jvm-dtest-forking" and
"test-jvm-dtest" maybe?
> Unit tests failure on trunk
> ---
>
> Key: CASSANDRA-15014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15014
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Dinesh Joshi
>Assignee: Alex Petrov
>Priority: Major
> Attachments: Screen Shot 2019-02-11 at 12.30.19.png, Screen Shot
> 2019-02-13 at 15.46.28.png, threads_stuck_waiting.png
>
>
> Currently org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> is failing on trunk with the following error -
> {code:java}
> [junit-timeout] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Exception in thread "main" java.lang.OutOfMemoryError:
> Metaspace
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest Tests run:
> 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest:readWithSchemaDisagreement:
> Caused an ERROR
> [junit-timeout] Forked Java VM exited abnormally. Please note the time in the
> report does not reflect the time until the VM exit.
> [junit-timeout] junit.framework.AssertionFailedError: Forked Java VM exited
> abnormally. Please note the time in the report does not reflect the time
> until the VM exit.
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.lang.Thread.run(Thread.java:748)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Test
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest FAILED
> (crashed)
> [junitreport] Processing /tmp/cassandra/build/test/TESTS-TestSuites.xml to
> /tmp/null1041131060
> [junitreport] Loading stylesheet
> jar:file:/usr/share/ant/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
> [junitreport] Transform time: 277ms
> [junitreport] Deleting: /tmp/null1041131060{code}
> I have noticed sporadic failures in the
> org.apache.cassandra.distributed.test.* suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15014) Unit tests failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767272#comment-16767272
]
Alex Petrov commented on CASSANDRA-15014:
-
[~jolynch] thank you for review
bq. "MigrationManager.announce" forever (screenshot attached)
I've just tried running tests myself and for me those threads stop, so I'm not
100% sure what's going on.
bq. Is test-distributed dead code?
It's just a more convenient runner, so that you wouldn't have to create a
testiest file.
bq. Unused imports in Instance.java
Fixed.
bq. Calling System.runFinalization() is interesting, did you try doing that
without the method separation and it didn't work?
I did try and it sometimes runs fine but isn't stable on non-high-capacity env.
I did runs on both environments before pushing. Also your run seems to have
passed.
bq. the only drawback I see is that our stdout will have "[exec]" prepended.
This is great, let's switch to what you propose.
> Unit tests failure on trunk
> ---
>
> Key: CASSANDRA-15014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15014
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Dinesh Joshi
>Assignee: Alex Petrov
>Priority: Major
> Attachments: Screen Shot 2019-02-11 at 12.30.19.png, Screen Shot
> 2019-02-13 at 15.46.28.png, threads_stuck_waiting.png
>
>
> Currently org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> is failing on trunk with the following error -
> {code:java}
> [junit-timeout] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Exception in thread "main" java.lang.OutOfMemoryError:
> Metaspace
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest Tests run:
> 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest:readWithSchemaDisagreement:
> Caused an ERROR
> [junit-timeout] Forked Java VM exited abnormally. Please note the time in the
> report does not reflect the time until the VM exit.
> [junit-timeout] junit.framework.AssertionFailedError: Forked Java VM exited
> abnormally. Please note the time in the report does not reflect the time
> until the VM exit.
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.lang.Thread.run(Thread.java:748)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Test
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest FAILED
> (crashed)
> [junitreport] Processing /tmp/cassandra/build/test/TESTS-TestSuites.xml to
> /tmp/null1041131060
> [junitreport] Loading stylesheet
> jar:file:/usr/share/ant/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
> [junitreport] Transform time: 277ms
> [junitreport] Deleting: /tmp/null1041131060{code}
> I have noticed sporadic failures in the
> org.apache.cassandra.distributed.test.* suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15014) Unit tests failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766676#comment-16766676
]
Joseph Lynch commented on CASSANDRA-15014:
--
[~ifesdjeen] I think that this is a pretty reasonable workaround, and from my
testing it only appears about 2x slower then running them all in one JVM (My
testing indicated about 1 min 10s vs 30s). I think long term we'll need to
figure out how to run these either with a fork per method or with a test
cluster per test class or something, but I recognize we're trying to mitigate
the trunk unit test runs here and we can iterate on making them faster next as
we need to.
Feedback:
* If we go generated script direction can we wrap up the gen list -> chmod ->
execute
[logic|https://github.com/apache/cassandra/compare/trunk...ifesdjeen:CASSANDRA-15014-trunk#diff-1d37e48f9ceff6d8030570cd36286a61R194]
into an ant target, the only drawback I see is that our stdout will have
"[exec]" prepended. Maybe something like
[this|https://github.com/apache/cassandra/commit/88da841585d4fb310bbac80b03601d74919fa507]
* Is
[test-distributed|https://github.com/apache/cassandra/compare/trunk...ifesdjeen:CASSANDRA-15014-trunk#diff-2cccd7bf48b7a9cc113ff564acd802a8R1890]
dead code?
* When I run `ant testclasslist
-Dtest.classlistfile=/home/josephl/pg/cassandra/testlist.txt
-Dtest.classlistprefix=distributed` to try to test if we need to split by
method and I attach yourkit it either fails with a class not found exception or
if I do attach I see a bunch of threads waiting on "MigrationManager.announce"
forever (screenshot attached). Can you run the test like that or do you hang as
well? I think this might indicate that the wait for logic in
AbstractCluster.java may not be working right
* Unused imports in
[Instance.java|https://github.com/apache/cassandra/compare/trunk...ifesdjeen:CASSANDRA-15014-trunk#diff-7c02c337a482a2dc284c2e67bbb44dc1R28]
* Calling System.runFinalization() is interesting, did you try doing that
without the method separation and it didn't work?
For trunk:
* Can you run it without the high capacity machines? Usually it's the unit
tests that fail
> Unit tests failure on trunk
> ---
>
> Key: CASSANDRA-15014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15014
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Dinesh Joshi
>Assignee: Alex Petrov
>Priority: Major
> Attachments: Screen Shot 2019-02-11 at 12.30.19.png,
> threads_stuck_waiting.png
>
>
> Currently org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> is failing on trunk with the following error -
> {code:java}
> [junit-timeout] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Exception in thread "main" java.lang.OutOfMemoryError:
> Metaspace
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest Tests run:
> 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest:readWithSchemaDisagreement:
> Caused an ERROR
> [junit-timeout] Forked Java VM exited abnormally. Please note the time in the
> report does not reflect the time until the VM exit.
> [junit-timeout] junit.framework.AssertionFailedError: Forked Java VM exited
> abnormally. Please note the time in the report does not reflect the time
> until the VM exit.
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.lang.Thread.run(Thread.java:748)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Test
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest FAILED
> (crashed)
> [junitreport] Processing /tmp/cassandra/build/test/TESTS-TestSuites.xml to
> /tmp/null1041131060
> [junitreport] Loading stylesheet
> jar:file:/usr/share/ant/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
> [junitreport] Transform time: 277ms
> [junitreport] Deleting: /tmp/null1041131060{code}
> I have noticed sporadic failures in the
> org.apache.cassandra.distributed.test.* suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15014) Unit tests failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765530#comment-16765530
]
Joseph Lynch commented on CASSANDRA-15014:
--
Heads up that non trunk links are missing the cassandra before the branch name
(e.g.
https://github.com/apache/cassandra/compare/2.2...ifesdjeen:CASSANDRA-15014-2.2
instead of
https://github.com/apache/cassandra/compare/cassandra-2.2...ifesdjeen:CASSANDRA-15014-2.2).
Working on review now.
> Unit tests failure on trunk
> ---
>
> Key: CASSANDRA-15014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15014
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Dinesh Joshi
>Assignee: Alex Petrov
>Priority: Major
> Attachments: Screen Shot 2019-02-11 at 12.30.19.png
>
>
> Currently org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> is failing on trunk with the following error -
> {code:java}
> [junit-timeout] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Exception in thread "main" java.lang.OutOfMemoryError:
> Metaspace
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest Tests run:
> 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest:readWithSchemaDisagreement:
> Caused an ERROR
> [junit-timeout] Forked Java VM exited abnormally. Please note the time in the
> report does not reflect the time until the VM exit.
> [junit-timeout] junit.framework.AssertionFailedError: Forked Java VM exited
> abnormally. Please note the time in the report does not reflect the time
> until the VM exit.
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.lang.Thread.run(Thread.java:748)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Test
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest FAILED
> (crashed)
> [junitreport] Processing /tmp/cassandra/build/test/TESTS-TestSuites.xml to
> /tmp/null1041131060
> [junitreport] Loading stylesheet
> jar:file:/usr/share/ant/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
> [junitreport] Transform time: 277ms
> [junitreport] Deleting: /tmp/null1041131060{code}
> I have noticed sporadic failures in the
> org.apache.cassandra.distributed.test.* suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15014) Unit tests failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764881#comment-16764881
]
Alex Petrov commented on CASSANDRA-15014:
-
In summary, there was a problem with retention resulting from schema change:
since it was executed on the main thread, we were retaining a bunch of thread
locals. Attaching a screenshot showing that we retain mere 12mb after full test
run.
I did test it on several environments and it seems that circleci is still
timing out because of GC pressure. I've decided to simplify runs and just have
each test executing in its own JVM to avoid GC contention alltogether.
I've also added an ant task to conveniently run distributed tests without test
list and have improved a shutdown process.
[patch|https://github.com/apache/cassandra/compare/trunk...ifesdjeen:CASSANDRA-15014-trunk]
[test
run|https://circleci.com/workflow-run/74627590-040f-49fd-91dd-912bdcef70de]
> Unit tests failure on trunk
> ---
>
> Key: CASSANDRA-15014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15014
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Dinesh Joshi
>Assignee: Alex Petrov
>Priority: Major
>
> Currently org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> is failing on trunk with the following error -
> {code:java}
> [junit-timeout] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Exception in thread "main" java.lang.OutOfMemoryError:
> Metaspace
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest Tests run:
> 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest:readWithSchemaDisagreement:
> Caused an ERROR
> [junit-timeout] Forked Java VM exited abnormally. Please note the time in the
> report does not reflect the time until the VM exit.
> [junit-timeout] junit.framework.AssertionFailedError: Forked Java VM exited
> abnormally. Please note the time in the report does not reflect the time
> until the VM exit.
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.lang.Thread.run(Thread.java:748)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Test
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest FAILED
> (crashed)
> [junitreport] Processing /tmp/cassandra/build/test/TESTS-TestSuites.xml to
> /tmp/null1041131060
> [junitreport] Loading stylesheet
> jar:file:/usr/share/ant/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
> [junitreport] Transform time: 277ms
> [junitreport] Deleting: /tmp/null1041131060{code}
> I have noticed sporadic failures in the
> org.apache.cassandra.distributed.test.* suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15014) Unit tests failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762980#comment-16762980
]
Dinesh Joshi commented on CASSANDRA-15014:
--
[~benedict] [~jolynch] [~ifesdjeen] could you please check whats going on?
> Unit tests failure on trunk
> ---
>
> Key: CASSANDRA-15014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15014
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Dinesh Joshi
>Priority: Major
>
> Currently org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> is failing on trunk with the following error -
> {code:java}
> [junit-timeout] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Exception in thread "main" java.lang.OutOfMemoryError:
> Metaspace
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest
> [junit-timeout] Testsuite:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest Tests run:
> 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest:readWithSchemaDisagreement:
> Caused an ERROR
> [junit-timeout] Forked Java VM exited abnormally. Please note the time in the
> report does not reflect the time until the VM exit.
> [junit-timeout] junit.framework.AssertionFailedError: Forked Java VM exited
> abnormally. Please note the time in the report does not reflect the time
> until the VM exit.
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.util.Vector.forEach(Vector.java:1275)
> [junit-timeout] at java.lang.Thread.run(Thread.java:748)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Test
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest FAILED
> (crashed)
> [junitreport] Processing /tmp/cassandra/build/test/TESTS-TestSuites.xml to
> /tmp/null1041131060
> [junitreport] Loading stylesheet
> jar:file:/usr/share/ant/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
> [junitreport] Transform time: 277ms
> [junitreport] Deleting: /tmp/null1041131060{code}
> I have noticed sporadic failures in the
> org.apache.cassandra.distributed.test.* suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
