Yep, sure. All these test groups can be triggered via system properties so sure -- a weekly build could enable the @Weekly group and run a full test. I don't know how heavy it is on the filesystem though (and if Jenkins can handle this particular test).
Dawid On Fri, Jun 29, 2012 at 12:46 PM, Robert Muir <[email protected]> wrote: > On Fri, Jun 29, 2012 at 6:31 AM, Dawid Weiss > <[email protected]> wrote: >>>> is annotated with this annotation. I don't know how slow it really is, >>> >>> couple of hours :) >> >> We need @SuperSlow. Or @YouWillTurnToDustBeforeItCompletes. >> >>> +1! Of course from time to time we should try to fix these slow tests >> >> Yep, it is unavoidable that the time will be increasing but we have >> the tools to collect stats periodically and we definitely should both >> try to decrease the time for the slowest tests and try to make life >> easier for developers by marking the slowest ones @Nightly and @Slow. >> I consider @Nightly stronger than @Slow because they're turned off by >> default. @Slow would be optional -- those who want a quick run can >> override it, those who don't care can run the full suite. >> >> I filed this issue: >> https://issues.apache.org/jira/browse/LUCENE-4181 >> >> I'm measuring the speed difference for the same seed out of curiosity, >> will apply shortly. >> > > I like the idea: maybe Test2BTerms should be @Weekly? I know we don't > use this (yet) in jenkins but the mechanism is there if someone wants > it right? > > > -- > lucidimagination.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
