cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-10035) Windows utest 3.0: TransactionLogsTest failure
Date Mon, 24 Aug 2015 04:42:45 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708767#comment-14708767
] 

Stefania edited comment on CASSANDRA-10035 at 8/24/15 4:41 AM:
---------------------------------------------------------------

Since CASSANDRA-7066 was committed, the tests have been failing less but we still have problems.
The first utest build on 3.0 with the patch committed was build #15. Since then:

* TransactionLogTest.testObsoletedDataFileUpdateTimeChanged failed on build 15
* TransactionLogTest.testWrongChecksumLastLineMissingFile failed on build 19
* TransactionLogTest.testRemoveUnfinishedLeftovers_abort and testRemoveUnfinishedLeftovers_commit
failed on build 22

The failure in build 15 is odd, it seems we did not pick up the modification of the last updated
time, we probably just need to release the sstables earlier.

The remaining failures are all related to listing temporary files, so I suspect the root cause
is CASSANDRA-10109.


was (Author: stefania):
Since CASSANDRA-7066 was committed, the tests have been failing less but we still have problems.
The first utest build on 3.0 with the patch committed was build #15. Since there:

* TransactionLogTest.testObsoletedDataFileUpdateTimeChanged failed on build 15
* TransactionLogTest.testWrongChecksumLastLineMissingFile failed on build 19
* TransactionLogTest.testRemoveUnfinishedLeftovers_abort and testRemoveUnfinishedLeftovers_commit
failed on build 22

The failure in build 15 is odd, it seems we did not pick up the modification of the last updated
time, we probably just need to release the sstables earlier.

The remaining failures are all related to listing temporary files, so I suspect the root cause
is CASSANDRA-10109.

> Windows utest 3.0: TransactionLogsTest failure
> ----------------------------------------------
>
>                 Key: CASSANDRA-10035
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10035
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Joshua McKenzie
>            Assignee: Stefania
>              Labels: Windows
>             Fix For: 3.0.0 rc1
>
>
> {noformat}
>     [junit] Testcase: testUntrack(org.apache.cassandra.db.lifecycle.TransactionLogsTest):
      FAILED
>     [junit] build\test\cassandra\data;0\TransactionLogsTest\mockcf4-6742d2103f8911e58737831ef068609c\ma-1-big-Data.db
>     [junit] junit.framework.AssertionFailedError: build\test\cassandra\data;0\TransactionLogsTest\mockcf4-6742d2103f8911e58737831ef068609c\ma-1-big-Data.db
>     [junit]     at org.apache.cassandra.db.lifecycle.TransactionLogsTest.assertFiles(TransactionLogsTest.java:575)
>     [junit]     at org.apache.cassandra.db.lifecycle.TransactionLogsTest.testUntrack(TransactionLogsTest.java:215)
>     [junit]
>     [junit]
>     [junit] Testcase: testAbortOnlyNew(org.apache.cassandra.db.lifecycle.TransactionLogsTest):
 FAILED
>     [junit] build\test\cassandra\data;0\TransactionLogsTest\mockcf5-67456a203f8911e58737831ef068609c\ma-0-big-Data.db
>     [junit] junit.framework.AssertionFailedError: build\test\cassandra\data;0\TransactionLogsTest\mockcf5-67456a203f8911e58737831ef068609c\ma-0-big-Data.db
>     [junit]     at org.apache.cassandra.db.lifecycle.TransactionLogsTest.assertFiles(TransactionLogsTest.java:575)
>     [junit]     at org.apache.cassandra.db.lifecycle.TransactionLogsTest.testAbortOnlyNew(TransactionLogsTest.java:312)
>     [junit]
>     [junit]
>     [junit] Testcase: testNoPrepare(org.apache.cassandra.db.lifecycle.TransactionLogsTest):
    FAILED
>     [junit] build\test\cassandra\data;0\TransactionLogsTest\mockcf13-675681203f8911e58737831ef068609c\ma-1-big-Data.db
>     [junit] junit.framework.AssertionFailedError: build\test\cassandra\data;0\TransactionLogsTest\mockcf13-675681203f8911e58737831ef068609c\ma-1-big-Data.db
>     [junit]     at org.apache.cassandra.db.lifecycle.TransactionLogsTest.assertFiles(TransactionLogsTest.java:575)
>     [junit]     at org.apache.cassandra.db.lifecycle.TransactionLogsTest.access$200(TransactionLogsTest.java:56)
>     [junit]     at org.apache.cassandra.db.lifecycle.TransactionLogsTest$TxnTest$Transaction.assertAborted(TransactionLogsTest.java:143)
>     [junit]     at org.apache.cassandra.db.lifecycle.TransactionLogsTest$TxnTest.assertAborted(TransactionLogsTest.java:191)
>     [junit]     at org.apache.cassandra.utils.concurrent.AbstractTransactionalTest.testNoPrepare(AbstractTransactionalTest.java:40)
> {noformat}
> taking the testPrepare case as an example: looks like it never passed on Windows ([history|http://cassci.datastax.com/view/trunk/job/trunk_utest_win32/lastCompletedBuild/testReport/org.apache.cassandra.db.lifecycle/TransactionLogsTest/testPrepare/history/])
> [~stefania_alborghetti]: annotate points to you on these tests. Care to take a look at
this?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message