Project-specific coverage data are partitioned. When running a test that involves multiple projects where test and app source may not reside in the same project, CloverDatabase logs at warning level for each test that can't be found for coverage data encoutnered. For projects with 1000s of tests, this can cause the Error Viewer to hog CPU. Pushing the warning to a verbose message until we have a cross-project solution in place.