Re: Use MockDirectoryFactory not RAMDirectoryFactory in test configs

2024-07-26 Thread Jason Gerlowski
+1 I took a crack at fixing this (on 'main' at least) here: https://github.com/apache/solr/pull/2598 Let me know what you guys think when you get a chance to review. On Sun, Jul 7, 2024 at 7:57 PM Jan Høydahl wrote: > > +1 > > Experienced the same locally, tried to override lock factory but did

Re: Use MockDirectoryFactory not RAMDirectoryFactory in test configs

2024-07-07 Thread Jan Høydahl
+1 Experienced the same locally, tried to override lock factory but did not dig deeper and ended up running some tests in gradle instead of IntelliJ. Annoying! Jan Høydahl > 1. juli 2024 kl. 22:57 skrev David Smiley : > > Some of our tests don't run correctly/consistently via IntelliJ's > int

Use MockDirectoryFactory not RAMDirectoryFactory in test configs

2024-07-01 Thread David Smiley
Some of our tests don't run correctly/consistently via IntelliJ's internal JUnit runner (compared to Gradle). IntelliJ's JUnit runner is faster and better integrated, saving developer productivity. I debugged the issue. The test TestInPlaceUpdatesDistrib failed because "RAMDirectory can only be