Re: [VOTE] Release Lucene 9.2.0 RC1

Alan noticed a backward compatibility issue in LUCENE-10312 and I'm working on it. I think respin would be needed - sorry for the additional work. Tomoko 2022年5月19日(木) 9:02 Patrick Zhai : > +1 SUCCESS! [1:12:17.482213] > > Thank you Alan! > > On Wed, May 18, 2022 at 4:31 PM Julie Tibshirani >

Re: [VOTE] Release Lucene 9.2.0 RC1

+1 SUCCESS! [1:12:17.482213] Thank you Alan! On Wed, May 18, 2022 at 4:31 PM Julie Tibshirani wrote: > +1 SUCCESS! [0:57:28.654665] > > Thanks Alan! > > On Wed, May 18, 2022 at 1:51 PM Anshum Gupta > wrote: > >> +1 SUCCESS! [0:59:19.002348] >> >> On Wed, May 18, 2022 at 5:59 AM Alan Woodward

Re: [VOTE] Release Lucene 9.2.0 RC1

+1 SUCCESS! [0:57:28.654665] Thanks Alan! On Wed, May 18, 2022 at 1:51 PM Anshum Gupta wrote: > +1 SUCCESS! [0:59:19.002348] > > On Wed, May 18, 2022 at 5:59 AM Alan Woodward > wrote: > >> Please vote for release candidate 1 for Lucene 9.2.0 >> >> The artifacts can be downloaded from: >> >>

Re: How to see test case logs in Intellij

Hi, Shah. I guess I see something like this recently. When I run Lucene test in intellyJ via gradle, debug view has two tabs: TestFooBar, :test. Stack and variables are shown in latter one but console output is shown in the former one. On Wed, May 18, 2022 at 9:27 PM Rushabh Shah wrote: > Hi

Re: [VOTE] Release Lucene 9.2.0 RC1

+1 SUCCESS! [0:59:19.002348] On Wed, May 18, 2022 at 5:59 AM Alan Woodward wrote: > Please vote for release candidate 1 for Lucene 9.2.0 > > The artifacts can be downloaded from: > > https://dist.apache.org/repos/dist/dev/lucene/lucene-9.2.0-RC1-rev-978eef5459c7683038ddcca4ec56e4baa63715d0 > >

Re: [VOTE] Release Lucene 9.2.0 RC1

+1 SUCCESS! [0:43:09.481661] I'm not going to get hung up on an issue with the smokeTester if Robert's not :) BTW thank you for running on slow machine that takes many hours! On Wed, May 18, 2022 at 3:48 PM Robert Muir wrote: > > I opened issue about this. It shouldn't block the release, but it

Re: How to see test case logs in Intellij

Also, IntelliJ can run tests in two modes - via gradle or directly. If you switch to direct mode, the logs should be printed without any additional properties. Dawid On Wed, May 18, 2022 at 8:53 PM Robert Muir wrote: > > Tests generally don't print or log anything. > > If you want them to print

Re: How to see test case logs in Intellij

Thank you Robert ! Rushabh Shah On Wed, May 18, 2022 at 11:52 AM Robert Muir wrote: > Tests generally don't print or log anything. > > If you want them to print tons of stuff, pass -Ptests.verbose=true to > gradle. > You can do it in idea IDE by going to "Run" menu, "Edit > Configurations",

Re: [VOTE] Release Lucene 9.2.0 RC1

I opened issue about this. It shouldn't block the release, but it is pretty crazy and something to improve. https://issues.apache.org/jira/browse/LUCENE-10579 On Wed, May 18, 2022 at 3:10 PM Robert Muir wrote: > > It seems strange the way that > confirmAllReleasesAreTestedForBackCompat() parses

Re: [VOTE] Release Lucene 9.2.0 RC1

It seems strange the way that confirmAllReleasesAreTestedForBackCompat() parses the output of the test's results, especially with test.verbose enabled. It uses regex to "look" for certain prints from the test in order to "see" that each release is tested. Maybe regex failed because something

Re: [VOTE] Release Lucene 9.2.0 RC1

The smoketester failed for me. Strange that it didn't fail for anyone else. My command line: $ export JAVA_HOME=/usr/lib/jvm/java-11-openjdk/ $ python3 -u dev-tools/scripts/smokeTestRelease.py --test-java17 /home/rmuir/Downloads/jdk

Re: How to see test case logs in Intellij

Tests generally don't print or log anything. If you want them to print tons of stuff, pass -Ptests.verbose=true to gradle. You can do it in idea IDE by going to "Run" menu, "Edit Configurations", and adding -Ptests.verbose=true to the command line of the particular test (e.g. TestDemo) On Wed,

How to see test case logs in Intellij

Hi Lucene devs, I am pretty new to the Lucene project and to the Gradle build tool also. When I run any test case via Intellij, I am not able to see any logs related to that test case. Do I need to set some special property in some config file to view the logs ? Please help. Thank you. Rushabh

Re: [VOTE] Release Lucene 9.2.0 RC1

+1 SUCCESS! [0:35:17.914586] Mike McCandless http://blog.mikemccandless.com On Wed, May 18, 2022 at 8:59 AM Alan Woodward wrote: > Please vote for release candidate 1 for Lucene 9.2.0 > > The artifacts can be downloaded from: > >

Re: Bugfix release Lucene/Solr 8.11.2

SOLR-16194 is in and ported to 8.11,.2 On Wed, May 18, 2022 at 7:12 AM Jan Høydahl wrote: > I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 because > I have an in-flight PR with a backport. I'll complete and merge that PR. > > Jan > > > 13. mai 2022 kl. 01:03 skrev Mike Drob :

[VOTE] Release Lucene 9.2.0 RC1

Please vote for release candidate 1 for Lucene 9.2.0 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-9.2.0-RC1-rev-978eef5459c7683038ddcca4ec56e4baa63715d0 You can run the smoke tester directly with this command: python3 -u

Re: Bugfix release Lucene/Solr 8.11.2

I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 because I have an in-flight PR with a backport. I'll complete and merge that PR. Jan > 13. mai 2022 kl. 01:03 skrev Mike Drob : > > To: dev@lucene, dev@solr > > NOTICE: > > I

Re: Lucene 9.2 release

Hi, I just wanted to note that I opened LUCENE-10578. Maybe it'd be worth having the discussion in Jira? 2022年5月18日(水) 18:31 Alan Woodward : > I think this release is the first time I’ve used Java 11 since 2019, yes! > > I’ll get the latest AdoptOpenJDK version and try and persuade my Mac to >

Re: Lucene 9.2 release

I think this release is the first time I’ve used Java 11 since 2019, yes! I’ll get the latest AdoptOpenJDK version and try and persuade my Mac to use it... > On 18 May 2022, at 10:19, Dawid Weiss wrote: > > Living in the past, aren't we? :) > > D. > > On Wed, May 18, 2022 at 10:49 AM Alan

RE: Lucene 9.2 release

Ah to add: OpenJDK releases do not vary between each other. The bugfix version numbers should be aligned. It may only happen that a specific vendor patches more security fixes in or adds optional features (like the Temurin ones have Shenandoah GC, Oracle's not). The tools like javac or javadoc

RE: Lucene 9.2 release

Hi Alan, I know the probem: This is the JDK 11 General Availability release (the first one that came out) and it is buggy to hell (also Lucene crashes hotspot with that one). This also has known issues with javadocs which were fixed in later bugfix versions. I think what you should do: Go To

Re: Lucene 9.2 release

Living in the past, aren't we? :) D. On Wed, May 18, 2022 at 10:49 AM Alan Woodward wrote: > > $ /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java -version > > openjdk version "11" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11+28) > OpenJDK 64-Bit Server VM 18.9

Re: Lucene 9.2 release

$ /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java -version openjdk version "11" 2018-09-25 OpenJDK Runtime Environment 18.9 (build 11+28) OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode) > On 18 May 2022, at 09:35, Dawid Weiss wrote: > > Alan, what's the exact JDK

Re: Lucene 9.2 release

Alan, what's the exact JDK vendor/ release number you used that had this problem? If we can reproduce it then we'd know where to look (bisect until we know javadoc works correctly). D. On Wed, May 18, 2022 at 10:33 AM Dawid Weiss wrote: > > > I'd like to draw attention to my second question

Re: Lucene 9.2 release

> I'd like to draw attention to my second question while we are still here... > should we limit the OpenJDK distribution (for building)? My worry here is, > that minor versions could depend on the distributor. This is a valid concern but it'd take some trial and error to verify which version

Re: Lucene 9.2 release

I'll take a look if I have a chance. I'd like to draw attention to my second question while we are still here... should we limit the OpenJDK distribution (for building)? My worry here is, that minor versions could depend on the distributor. 2022年5月18日(水) 16:10 Dawid Weiss : > I think it makes

Re: Lucene 9.2 release

I think it makes sense to fail the build in both cases. An early warning to upgrade buggy old java releases... D. On Wed, May 18, 2022 at 9:06 AM Tomoko Uchida wrote: > > Thanks, Dawid for the pointer. > If there is a distribution-agnostic and reliable minor/patch version, we > could specify a

Re: Lucene 9.2 release

Thanks, Dawid for the pointer. If there is a distribution-agnostic and reliable minor/patch version, we could specify a more detailed minimum requirement version for building. I think we shouldn't limit the distribution - or, we should (at least on making the release artifact)? Tomoko

Re: Lucene 9.2 release

> I'd agree with this and it'd be great if we can fail to build locally and > encourage devs to use a newer patch version of Java (instead of blaming > developers for not upgrading jdk they use) - I have no good idea at all > though. This should be simple. In alternative-jdk-support.gradle,