[
https://issues.apache.org/jira/browse/LUCENE-9818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss resolved LUCENE-9818.
---------------------------------
Fix Version/s: master (9.0)
Resolution: Fixed
> add option or hack or patch to see "slowest test suites"
> --------------------------------------------------------
>
> Key: LUCENE-9818
> URL: https://issues.apache.org/jira/browse/LUCENE-9818
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Priority: Major
> Fix For: master (9.0)
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently we print the N slowest test methods at the end of the run, which is
> great.
> Can we add some way (even if hacky and just a patch we don't commit) to see
> the N slowest *suites*? Ideally it would sum the times of all test methods
> and beforeClass/afterClass stuff too.
> It would help spot test classes doing pathological indexing in beforeClass(),
> which isn't captured today I think? Also you can spot big test classes as a
> whole, which might mean there is something inefficient about the design of
> the whole class (e.g. it should use beforeClass() instead of setup() if all
> methods just use the same index). Maybe each method takes 2s but it has 50 of
> them, for example.
> cc [~dweiss] just an idea I had while working on LUCENE-9817
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
