Thank you for the details and for taking the time to illustrate with a PR. This worked like a charm. Perhaps someday it might be nice to add a gradle option to easily enable solr.log output. I imagine this would be helpful in a lot of cases.
(While I am writing I also want to thank you for helping clean up from the mess I made with PR 2086 a few weeks ago!) On Thu, Dec 14, 2023 at 1:50 AM Mikhail Khludnev <m...@apache.org> wrote: > > Hi James, > Turns out it's not easy > https://github.com/apache/solr/pull/2153/ > I had to copy log4j2.xml from core (not tests', tests log to console only) > AND then remove <Async stuff in favor of plain one > Then it needs to pass solr.log.dir via build.gradle (command line args > don't work either, as well as default placeholder) > After that I > noticed solr\solrj-streaming\build\tmp\tests-cwd\stuff\solr.log appear and > contains logs from all nodes. > Perhaps I missed something, but so far it seems quite cumbersome. Hope it > helps. > > On Thu, Dec 14, 2023 at 3:59 AM James Dyer <jdyer....@gmail.com> wrote: > > > I am trying to look at the many test failures we have for > > "CloudAuthStreamTest". > > This test spins up 2 solrcloud clusters with several cores each. One thing > > that might help me out is if I could inspect the "solr.log" for each of the > > cores. But I am not finding the logs anywhere. Can anyone give me hints > > as to where I should look, or possibly what I can do to get it to output > > the logs? The best thing, is if I could get all the log lines nicely > > labeled in standard out when running with "-Ptests.verbose=true". Is there > > a known way to achieve this? > > > > > -- > Sincerely yours > Mikhail Khludnev --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
