Wow you have a fast machine! You are correct on the unsupported/module front :-( But it is tough since I would like the unsupported modules to be more for experiements (and by not running their tests we have less chance of them breaking out build). It is too bad we could not have the daily build box run the reports for them (junit and coverage) - since it is based on coverage tests that they can move to supported status.
Thanks for your thoughts; and absolute time on a build box sounds like the most fair and public benchmark we could provide. Jody > Jody Garnett ha scritto: >> Andrea+1 If the build takes too long it does not get performed (we >> end up depending on the build box instead). >> >> We did try and provide a guidelines for build times in the developer >> guide (this is part of what I asked for a review of on Monday). >> - http://docs.codehaus.org/display/GEOT/5.+7+Testing >> >> Andrea could you help refine this page; to something sensible we can >> achive. > > I'll try... sigh, I have a list of things to do that does not fit > anymore a 20" screen (and it's written in 8pt char). > >> Can I ask the following ... >> - your build times reported: did this include testing? Or was it >> simply to compile? > > mvn clean install > >> - I would like to shoot for 5 mins as a target - is this resonable? > > 5 minutes for what? Which hardware? > Some sort of ratio maybe... each module > should not take more than x% of the total build time. > This would at least be hardware independent. Say, no more than 5% > or the build time, or a lower percentage > (that would be 30 seconds on my PC). > Or else, if build boxes are not loaded with anything else, we could > use the build boxes timings and set an absolute limit. > Anyways, that should be per module, since the number of modules is > growing, otherwise each time a module is added we require other modules > to reduce their testing times... > >> - I would really like to turn off testing for unsupported modules >> (both to shorten the build time, and to provide a reason for module >> maintainers to put in the effort) > > Here I disagree. You would convey the opposite message, that is, > staying in unsupported you dont' really need tests, nobody will > run them anyways. > Cheers > Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
