Re: junit - previous test run data not cleared
This is not a bug, see: https://issues.apache.org/jira/browse/LUCENE-4654 what you see are averages from locally collected statistics. They have been moved from temporary folders to allow better approximation of build times on CI servers (where ant clean usually takes place in between builds). If you want to remove previous stats (or make them volatile and removed after ant clean), make a user-default for any of the following properties: property name=local.caches location=${common.dir}/../.caches / property name=tests.cachedir location=${local.caches}/test-stats / If you place that folder under a build it'll be successively removed after an ant clean. Dawid On Mon, May 20, 2013 at 7:52 AM, Shawn Heisey s...@elyograg.org wrote: I noticed something a little odd -- certain test data is not cleared up by the clean target. At some point in the past, I ran all the tests. Today, while running an individual test case, I see tophint data from other tests. I was in solr/solrj and ran -Dtestcase=NamedListTest. This is the last part of the output: [junit4:junit4] Executing 1 suite with 1 JVM. [junit4:junit4] [junit4:junit4] Started J0 PID(6384@freya). [junit4:junit4] Suite: org.apache.solr.common.util.NamedListTest [junit4:junit4] OK 0.13s | NamedListTest.testRecursive [junit4:junit4] OK 0.01s | NamedListTest.testRemove [junit4:junit4] Completed in 0.79s, 2 tests [junit4:junit4] [junit4:junit4] JVM J0: 0.87 .. 2.25 = 1.38s [junit4:junit4] Execution time total: 2.26 sec. [junit4:junit4] Tests summary: 1 suite, 2 tests [echo] 5 slowest tests: [junit4:tophints] 40.21s | org.apache.solr.client.solrj.impl.CloudSolrServerTest [junit4:tophints] 38.67s | org.apache.solr.client.solrj.TestLBHttpSolrServer [junit4:tophints] 23.83s | org.apache.solr.client.solrj.embedded.SolrExampleStreamingTest [junit4:tophints] 15.20s | org.apache.solr.client.solrj.embedded.SolrExampleStreamingBinaryTest [junit4:tophints] 7.96s | org.apache.solr.client.solrj.TestBatchUpdate BUILD SUCCESSFUL Total time: 11 seconds As you can see, the tophints data was all from tests that I didn't run this time. It happens on both Linux and Windows, and for tests under lucene as well as solr. Is this a known problem with no simple solution, or should I file an issue? Thanks, Shawn - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: junit - previous test run data not cleared
On 5/19/2013 11:52 PM, Shawn Heisey wrote: As you can see, the tophints data was all from tests that I didn't run this time. It happens on both Linux and Windows, and for tests under lucene as well as solr. After I sent this, I noted the existence of a .cache directory with many timehints.txt files. This tickled a memory about test timing statistics that survive multiple test runs on jenkins. I can think of two ways to approach fixing this cosmetic problem that don't involve losing the statistics. We could implement one or both of them: The first idea is to have the display of tophints data reflect only the tests that were actually run, not the cached data about every test in the group. The second idea touches on another topic that interests me -- having a build target that will return the tree to a completely pristine state, just like when it is first checked out from svn. I just saw Dawid's reply. It confirmed my vague memory. Thanks for the info about tweaking my local install, I will look into that. Thanks, Shawn - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
junit - previous test run data not cleared
I noticed something a little odd -- certain test data is not cleared up by the clean target. At some point in the past, I ran all the tests. Today, while running an individual test case, I see tophint data from other tests. I was in solr/solrj and ran -Dtestcase=NamedListTest. This is the last part of the output: [junit4:junit4] Executing 1 suite with 1 JVM. [junit4:junit4] [junit4:junit4] Started J0 PID(6384@freya). [junit4:junit4] Suite: org.apache.solr.common.util.NamedListTest [junit4:junit4] OK 0.13s | NamedListTest.testRecursive [junit4:junit4] OK 0.01s | NamedListTest.testRemove [junit4:junit4] Completed in 0.79s, 2 tests [junit4:junit4] [junit4:junit4] JVM J0: 0.87 .. 2.25 = 1.38s [junit4:junit4] Execution time total: 2.26 sec. [junit4:junit4] Tests summary: 1 suite, 2 tests [echo] 5 slowest tests: [junit4:tophints] 40.21s | org.apache.solr.client.solrj.impl.CloudSolrServerTest [junit4:tophints] 38.67s | org.apache.solr.client.solrj.TestLBHttpSolrServer [junit4:tophints] 23.83s | org.apache.solr.client.solrj.embedded.SolrExampleStreamingTest [junit4:tophints] 15.20s | org.apache.solr.client.solrj.embedded.SolrExampleStreamingBinaryTest [junit4:tophints] 7.96s | org.apache.solr.client.solrj.TestBatchUpdate BUILD SUCCESSFUL Total time: 11 seconds As you can see, the tophints data was all from tests that I didn't run this time. It happens on both Linux and Windows, and for tests under lucene as well as solr. Is this a known problem with no simple solution, or should I file an issue? Thanks, Shawn - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org