[ 
https://issues.apache.org/jira/browse/CASSANDRA-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-7712:
--------------------------------------
    Attachment: 7712-hung-CliTest_system.log.gz

I didn't get terribly far due to CliTest hanging with this patch applied to 
cassandra-2.0 branch. It appears to go through the test, then "Announcing 
shutdown", then a bunch of java.io.FileNotFoundException for .db files in 
TestKeySpace and never completes shutting down. Same result on several 
different systems - debug system.log for just the CliTest attached.

> temporary files need to be cleaned by unit tests
> ------------------------------------------------
>
>                 Key: CASSANDRA-7712
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7712
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tests
>            Reporter: Michael Shuler
>            Priority: Minor
>              Labels: bootcamp, lhf
>             Fix For: 2.0.11
>
>         Attachments: 7712-hung-CliTest_system.log.gz, 7712-v2.txt, 
> CASSANDRA-7712_apache_cassandra_2.0.txt
>
>
> There are many unit test temporary files left behind after test runs. In the 
> case of CI servers, I have seen >70,000 files accumulate in /tmp over a 
> period of time. Each unit test should make an effort to remove its temporary 
> files when the test is completed.
> My current unit test cleanup block:
> {noformat}
> # clean up after unit tests..
> rm -rf  /tmp/140*-0 /tmp/CFWith* /tmp/Counter1* /tmp/DescriptorTest* 
> /tmp/Keyspace1* \
>         /tmp/KeyStreamingTransferTestSpace* /tmp/SSTableExportTest* 
> /tmp/SSTableImportTest* \
>         /tmp/Standard1* /tmp/Statistics.db* /tmp/StreamingTransferTest* 
> /tmp/ValuesWithQuotes* \
>         /tmp/cassandra* /tmp/jna-* /tmp/ks-cf-ib-1-* /tmp/lengthtest* 
> /tmp/liblz4-java*.so /tmp/readtest* \
>         /tmp/set_length_during_read_mode* /tmp/set_negative_length* 
> /tmp/snappy-*.so
> {noformat}



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

Reply via email to