cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-3841) long-test timing out
Date Tue, 18 Sep 2012 05:19:07 GMT

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

Jason Brown edited comment on CASSANDRA-3841 at 9/18/12 4:18 PM:
-----------------------------------------------------------------

I was able to reproduce the originally reported error - it was just the junit test timing
out. The previous time limit was 300000 ms (5 minutes), and I increased it to 600000 ms (10
minutes).

However, I was not able to reproduce Jonathan's reported problems, even after executing a
run of all the individual tests:

{code}for i in LongTableTest MeteredFlusherTest LongCompactionSpeedTest LongBloomFilterTest
LongLegacyBloomFilterTest; \
do ant clean long-test -Dtest.name=$i; done{code}
                
      was (Author: jasobrown):
    I was able to reproduce the originally reported error - it was just the junit test timing
out. The previous time limit was 300000 ms (5 minutes), and I increased it to 600000 ms (10
minutes).

However, I was not able to reproduce Jonathan's reported problems, even after executing a
run of all the individual tests:

for i in LongTableTest MeteredFlusherTest LongCompactionSpeedTest LongBloomFilterTest LongLegacyBloomFilterTest;
do ant clean long-test -Dtest.name=$i; done
                  
> long-test timing out
> --------------------
>
>                 Key: CASSANDRA-3841
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3841
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.1.0
>            Reporter: Michael Allen
>            Assignee: Jason Brown
>            Priority: Minor
>             Fix For: 1.1.6
>
>         Attachments: 0001-CASSANDRA-3841-long-test-timing-out.patch
>
>
>     [junit] ------------- ---------------- ---------------
>     [junit] Testsuite: org.apache.cassandra.db.compaction.LongCompactionSpeedTest
>     [junit] Testsuite: org.apache.cassandra.db.compaction.LongCompactionSpeedTest
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
>     [junit] 
>     [junit] Testcase: org.apache.cassandra.db.compaction.LongCompactionSpeedTest:BeforeFirstTest:
Caused an ERROR
>     [junit] Timeout occurred. Please note the time in the report does not reflect the
time until the timeout.
>     [junit] junit.framework.AssertionFailedError: Timeout occurred. Please note the time
in the report does not reflect the time until the timeout.
>     [junit] 
>     [junit] 
>     [junit] Test org.apache.cassandra.db.compaction.LongCompactionSpeedTest FAILED (timeout)
>     [junit] Testsuite: org.apache.cassandra.utils.LongBloomFilterTest
>     [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 64.536 sec
>     [junit] 
>     [junit] Testsuite: org.apache.cassandra.utils.LongLegacyBloomFilterTest
>     [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 41.104 sec
>     [junit] 
> BUILD FAILED
> /Users/mallen/dstax/repos/git/cassandra/build.xml:1113: The following error occurred
while executing this line:
> /Users/mallen/dstax/repos/git/cassandra/build.xml:1036: Some long test(s) failed.
> Total time: 63 minutes 9 seconds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message