Hi Mike,
Are you trying to run *all* the tests from Lucene from IntelliJ? I admit I
haven't tried that... :) I usually use intellij for running/ debugging
isolated classes, then rerun the full suite from command line (increased
parallelism). I don't think everything will work - if something needs
Hi folks,
I was wondering if people had experimented with something other than the
default Lucene search logic of completing one segment within a Slice at a
time, and then going on to the next segment in sequential order.
Here is the current logic in IndexSearcher#search(List
leaves, Weight weigh
I'm also getting errors like:
Caused by: java.lang.ExceptionInInitializerError: Exception
java.lang.LinkageError: MemorySegmentIndexInputProvider is missing in
Lucene JAR file [in thread
"TEST-TestDemo.testDemo-seed#[872544629C2881C6]"]
I wonder if this is due to some kind of module permissions t
hm I found FakeCharFilterFactory in src/test/META-INF.services -- it's
in a "test sources root" folder and won't allow itself to be set as a
resources folder? hm even after fiddling with this - I finally get to
mark it as "test resources root" my test is still not passing. This
can't be this hard!
hmm so after playing around with this Intellij build for a bit I ran
into some trouble -- all the tests relying on SPI seemed to start
failing. So then I switched back to build with Gradle and rebuild the
project and these tests passed. Just to double check there wasn't some
strange stale build pro
ok, life must be scary for developers on windows!
On Fri, Jun 7, 2024 at 10:33 AM Dawid Weiss wrote:
>
>
> Certain regenerate tasks do require perl and python indeed.
>
> On Fri, Jun 7, 2024 at 2:23 PM Michael Sokolov wrote:
>>
>> While editing this CONTRIBUTING.md I found the following statemen
Certain regenerate tasks do require perl and python indeed.
On Fri, Jun 7, 2024 at 2:23 PM Michael Sokolov wrote:
> While editing this CONTRIBUTING.md I found the following statement:
>
> Some build tasks (in particular `./gradlew check`) require Perl
> and Python 3.
>
> Is it actually true
While editing this CONTRIBUTING.md I found the following statement:
Some build tasks (in particular `./gradlew check`) require Perl
and Python 3.
Is it actually true that we require Perl?
On Fri, Jun 7, 2024 at 8:11 AM Michael Sokolov wrote:
>
> So I'm glad we have a fix for this, but it's
So I'm glad we have a fix for this, but it's making me realize that
any new joiner that uses intellij (probably most of them?) will have
this problem and have no idea what to do about it. They will just
conclude - running Lucene tests in intellij sucks. If we revived that
intellij target maybe that
+1, I had the same problem and it seems better now. Thank you, Dawid!
On Thu, 6 Jun 2024 at 12:20, Michael Sokolov wrote:
> Oh! TIL! so much better, thanks. And now I have the "Repeat" option
> back in the test runner
>
> On Thu, Jun 6, 2024 at 6:18 AM Dawid Weiss wrote:
> >
> >
> > Don't know
10 matches
Mail list logo
