You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Shuler (JIRA)" <ji...@apache.org> on 2013/11/08 18:48:17 UTC
[jira] [Updated] (CASSANDRA-6321) Unit Tests Failing in trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-6321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Shuler updated CASSANDRA-6321:
--------------------------------------
Description:
Many unit tests are failing in trunk [0] due to a timeout, but there are relatively few in the cassandra-2.0 branch [1].
I bisected the first test failure, CacheProviderTest, to commit:
{code}
((6c9efb0...)|BISECTING)mshuler@mana:~/DataStax/repos/cassandra$ git bisect good
a552b305f3d1b17e394744b18efd7f40599f3c2e is the first bad commit
commit a552b305f3d1b17e394744b18efd7f40599f3c2e
Author: Sylvain Lebresne <sy...@datastax.com>
Date: Thu Sep 19 09:20:13 2013 +0200
Add user-defined types to CQL3
patch by slebresne; reviewed by iamaleskey for CASSANDRA-5590
:100644 100644 e55c8f79d66e91e896dc5ef1f0b7567b03e3910b 4231b0b1a42a2d243fd6bcd9367ab7299f6ce680 M CHANGES.txt
:040000 040000 b838b9b052f19eafe2f927188f8c46a48feae01e c44978f3a5e2c69333fb7036a32b5f8a81f5d28a M src
{code}
It is possible that the large number of subsequent failures may be due to some of the substantial changes in the addition of user types (? that's a guess). I will see if I can bisect and identify some other individual test failures, but wanted to get this general ticket started.
Example trunk unit test:
[0] http://buildbot.datastax.com:8020/builders/trunk/builds/2531/steps/shell/logs/stdio
Example 2.0 unit test:
[1] http://buildbot.datastax.com:8020/builders/cassandra-2.0/builds/340/steps/shell/logs/stdio
Thanks!
Michael Shuler
was:
Many unit tests are failing in trunk [0] due to a timeout, but there are relatively few in the cassandra-2.0 branch [1].
I bisected the first test failure, CacheProviderTest, to commit:
{code}
((6c9efb0...)|BISECTING)mshuler@mana:~/DataStax/repos/cassandra$ git bisect good
a552b305f3d1b17e394744b18efd7f40599f3c2e is the first bad commit
commit a552b305f3d1b17e394744b18efd7f40599f3c2e
Author: Sylvain Lebresne <sy...@datastax.com>
Date: Thu Sep 19 09:20:13 2013 +0200
Add user-defined types to CQL3
patch by slebresne; reviewed by iamaleskey for CASSANDRA-5590
:100644 100644 e55c8f79d66e91e896dc5ef1f0b7567b03e3910b 4231b0b1a42a2d243fd6bcd9367ab7299f6ce680 M CHANGES.txt
:040000 040000 b838b9b052f19eafe2f927188f8c46a48feae01e c44978f3a5e2c69333fb7036a32b5f8a81f5d28a M src
{code}
It is possible that the large number of subsequent failures may be due to some of the substantial changes in the addition of user types (? that's a guess). I will see if I can bisect and identify some other individual test failures, but wanted to get this general ticket started.
Example trunk unit test:
[0] http://buildbot.datastax.com:8020/builders/trunk/builds/2531/steps/shell/logs/stdio
Example 2.0 unit test:
http://buildbot.datastax.com:8020/builders/cassandra-2.0/builds/340/steps/shell/logs/stdio
Thanks!
Michael Shuler
> Unit Tests Failing in trunk
> ---------------------------
>
> Key: CASSANDRA-6321
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6321
> Project: Cassandra
> Issue Type: Test
> Components: Tests
> Environment: Debian Wheezy, Oracle Java 1.7.0_25 (buildbot.datastax.com VM)
> Reporter: Michael Shuler
> Priority: Minor
>
> Many unit tests are failing in trunk [0] due to a timeout, but there are relatively few in the cassandra-2.0 branch [1].
> I bisected the first test failure, CacheProviderTest, to commit:
> {code}
> ((6c9efb0...)|BISECTING)mshuler@mana:~/DataStax/repos/cassandra$ git bisect good
> a552b305f3d1b17e394744b18efd7f40599f3c2e is the first bad commit
> commit a552b305f3d1b17e394744b18efd7f40599f3c2e
> Author: Sylvain Lebresne <sy...@datastax.com>
> Date: Thu Sep 19 09:20:13 2013 +0200
> Add user-defined types to CQL3
>
> patch by slebresne; reviewed by iamaleskey for CASSANDRA-5590
> :100644 100644 e55c8f79d66e91e896dc5ef1f0b7567b03e3910b 4231b0b1a42a2d243fd6bcd9367ab7299f6ce680 M CHANGES.txt
> :040000 040000 b838b9b052f19eafe2f927188f8c46a48feae01e c44978f3a5e2c69333fb7036a32b5f8a81f5d28a M src
> {code}
> It is possible that the large number of subsequent failures may be due to some of the substantial changes in the addition of user types (? that's a guess). I will see if I can bisect and identify some other individual test failures, but wanted to get this general ticket started.
> Example trunk unit test:
> [0] http://buildbot.datastax.com:8020/builders/trunk/builds/2531/steps/shell/logs/stdio
> Example 2.0 unit test:
> [1] http://buildbot.datastax.com:8020/builders/cassandra-2.0/builds/340/steps/shell/logs/stdio
> Thanks!
> Michael Shuler
--
This message was sent by Atlassian JIRA
(v6.1#6144)