Howdy devs, I stumbled onto https://issues.apache.org/jira/browse/SOLR-16304 while trying to upgrade our Lucene dependency and it's motivated me to take a little bit of a look at our tests. I know that there are dragons here and I'm under no illusions that I can fix everything, but I feel like a thorough audit might be useful.
The short of it is that @Slow is going away. We have choices on what to do. We currently have 112 tests annotated as such. Let's start with some definitions? What is our threshold for how slow is @Slow? Obviously this will vary from machine to machine, but maybe let's say that anything under 10s on my 2017 iMac Pro is fast and anything longer is slow? Arbitrary, and I reserve the right to move this later if I feel there's a better cut off. So maybe some tests get a new breath on life by being unlabelled. Maybe some other ones get fixed (reducing data size is one idea...) Some tests are slow because we have distributed systems and propagation delay and lots of gross sleeps and waits, and I don't want to touch those. Maybe those become Nightlies. Are there other approaches? What do folks want to do to move us forward? Mike
