[
https://issues.apache.org/jira/browse/LUCENE-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166917#comment-14166917
]
Dawid Weiss commented on LUCENE-6002:
-------------------------------------
No. There are no "meta" support annotations. You need to apply them separately
to each class annotated with Monster. Note that suite timeout applies to entire
suites, not individual test cases. The easiest way to accomplish that would be
to isolate a superclass MonsterTestCase from which all the monsters would
inherit. Call it a mother-monster if you will. Then apply any annotation on
that superclass (they are inherited).
All annotations (and the test runner/ code) are part of the randomizedtesting
project and have nothing to do whatsoever with what we do in the open source
(Carrot2) or commercially (Carrot Search). Do not spread confusion, it stays on
the internet ;).
https://github.com/carrotsearch/randomizedtesting
> Fix monster tests so they pass
> ------------------------------
>
> Key: LUCENE-6002
> URL: https://issues.apache.org/jira/browse/LUCENE-6002
> Project: Lucene - Core
> Issue Type: Bug
> Components: general/test
> Affects Versions: 5.0
> Environment: Linux sauron 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3
> 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.7.0_67"
> Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
> AMD Phenom(tm) II X3 705e, 2.5Ghz
> 12GB RAM
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Fix For: 5.0, Trunk
>
>
> The tests labelled @Monster are having a very hard time passing. Initially,
> there were some real failures on tests that push the 2 billion envelope, as
> well as some test bugs regarding suite timeouts and the quantity of date sent
> to sysout. [~mikemccand] committed a fix for the real failures and the
> initial sysout problems.
> Trying to move @SuppressSysoutChecks to the definition of @Monster didn't
> work. I'm also having trouble defining the suite timeouts. One test that
> says it takes about 45 minutes hit the six hour timeout that I had configured
> for the suite, and failed.
> What sort of machine should we use as a "normal" machine for deciding on
> suite timeouts? My machine is over four years old, but it's got three 2.5Ghz
> cores and 12GB of RAM. That's certainly not a completely modern machine, but
> it's not exactly slow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
