Something is fishy with this sudden onset of RegexBoostProcessorTest
failures....
- happening on diff hosts, diff OSes, diff JVMs
- happening on trunk and 4x
- only started happening today
- SolrRequestParsers object is huge for no explicible reason...
: Stack Trace: junit.framework.AssertionFailedError: Clean up static
: fields (in @AfterClass?), your test seems to hang on to approximately
: 51,150,032 bytes (threshold is 10,485,760). Field reference sizes
: (counted individually):
...
: - 51,880,376 bytes, protected static
: org.apache.solr.servlet.SolrRequestParsers
: org.apache.solr.update.processor.RegexBoostProcessorTest._parser
...why is SolrRequestParsers 51 MB ?
In other similar failures today it was 11MB, 12MB, 25MB, etc...
Instances of this class shouldn't by fluctuating in size, it doesn't
maintain any mutable state -- so WTF?
Don't get me wrong: RegexBoostProcessorTest should probably have an
@AfterClass to null this out -- but i'm concerned that either:
a) something has changed allowing SolrRequestParsers instances to now
grow w/o bound
b) something has changed to break the size detection code in the test
framework.
...anybody have any idea what changed?
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
