Andrea Aime wrote: > Main takes time because it's big and whatnot, yet there is a specific > test that it's slow, and hits only windows (there is a check for the > operating system in the tests, the slow part is skipped on unix): > DataUtilitiesTest.testUrlToFile. > In that test an attempt to access a network share is made > in handleFile( "\\\\host\\share\\file" ). Removing that check > brings the build time from 32 to 19 seconds on my pc.... We can move this to extensive - I am happy the functionality works as advertised now (that was the only reason I wrote the test case). > I'm wondering if we should mark that one as "extensive" too. > The trouble is that extensive tests are run only during releases, > so that test would be run only if the person releasing is > running tests on windows. That would be me :-) > In validation and gml3 I noticed there are single tests taking > 5-10 seconds, so they may be candidate for slim down (maybe > they are using too much data) or be moved to extensive? I think that would be the one test I left in there to do the nested for loop solution for joins; and as such it has some value. I believe the data sizes are small however. > > Besides that, all tests are building simple features and we > know that become much slower on trunk, so build times are probably > going to get down a little when someone finds time to optimize out > the current implementation. Thanks for your care and attention on this one Andrea. Jody
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
