mirror of
https://github.com/apache/lucene.git
synced 2025-02-10 12:05:36 +00:00
b335034615
When we are creating a new thread we should give it a descriptive name and enforce this via ForbiddenAPIs. This doesn't apply to Runnable or Callable objects that we pass to an executor, since those should be getting named by the executor itself. We don't require this in tests because the tests should be more self contained and there is less benefit in descriptive names. If somebody is already profiling a test, then they likely have the context to understand what the unnamed threads are doing, whereas a thread dump from a running Solr instance should have good thread names for everything. This is especially helpful when doing profiling, otherwise we end up with a bunch of Thread-# that are hard to tell apart and search on.
The Solr test-framework products base classes and utility classes for writting JUnit tests excercising Solr functionality.
This test framework relies on the lucene components found in in the ./lucene-libs/ directory, as well as the third-party libraries found in the ./lib directory.