Re: [JENKINS] Lucene-9.x-Linux (64bit/hotspot/jdk-11.0.21) - Build # 14204 - Unstable!

2023-12-01 Thread Patrick Zhai 
Seems it's because this MockRandomMergePolicy change

recently
makes ParallelLeafReader unhappy - it's reading two parallel segments from
2 dir and this MP makes one of the segments' documents order reversed.

But should be just test util issue and not affecting release.

Adrien do you want to take a look? I'm not sure what's the best way to fix
it, adding an index sort for that test seems a bit overkill?

Patrick

On Fri, Dec 1, 2023 at 2:06 PM Michael McCandless 
wrote:

> Hmm this reproduces for me, and looks new/unique.  Could it be related to
> recent 9.9.0 changes / release blocker?
>
> Mike
>
> On Fri, Dec 1, 2023 at 3:33 PM Policeman Jenkins Server <
> jenk...@thetaphi.de> wrote:
>
>> Build: https://jenkins.thetaphi.de/job/Lucene-9.x-Linux/14204/
>> Java: 64bit/hotspot/jdk-11.0.21 -XX:+UseCompressedOops -XX:+UseParallelGC
>>
>> 1 tests failed.
>> FAILED:  org.apache.lucene.index.TestParallelLeafReader.testQueries
>>
>> Error Message:
>> org.junit.ComparisonFailure: expected: but was:
>>
>> Stack Trace:
>> org.junit.ComparisonFailure: expected: but was:
>> at
>> __randomizedtesting.SeedInfo.seed([6CA57EA3FB50CA0D:302BB278E1397FA3]:0)
>> at org.junit.Assert.assertEquals(Assert.java:117)
>> at org.junit.Assert.assertEquals(Assert.java:146)
>> at
>> org.apache.lucene.index.TestParallelLeafReader.queryTest(TestParallelLeafReader.java:263)
>> at
>> org.apache.lucene.index.TestParallelLeafReader.testQueries(TestParallelLeafReader.java:48)
>> at
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> at
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>> at
>> com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
>> at
>> com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
>> at
>> com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
>> at
>> com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
>> at
>> org.apache.lucene.tests.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:48)
>> at
>> org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
>> at
>> org.apache.lucene.tests.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
>> at
>> org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
>> at
>> org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
>> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>> at
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at
>> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
>> at
>> com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:843)
>> at
>> com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:490)
>> at
>> com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
>> at
>> com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
>> at
>> com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
>> at
>> com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
>> at
>> org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
>> at
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at
>> org.apache.lucene.tests.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
>> at
>> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
>> at
>> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
>> at
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at
>> org.apache.lucene.tests.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
>>

Re: [JENKINS] Lucene-9.x-Linux (64bit/hotspot/jdk-11.0.21) - Build # 14204 - Unstable!

2023-12-01 Thread Michael McCandless 
Hmm this reproduces for me, and looks new/unique.  Could it be related to
recent 9.9.0 changes / release blocker?

Mike

On Fri, Dec 1, 2023 at 3:33 PM Policeman Jenkins Server 
wrote:

> Build: https://jenkins.thetaphi.de/job/Lucene-9.x-Linux/14204/
> Java: 64bit/hotspot/jdk-11.0.21 -XX:+UseCompressedOops -XX:+UseParallelGC
>
> 1 tests failed.
> FAILED:  org.apache.lucene.index.TestParallelLeafReader.testQueries
>
> Error Message:
> org.junit.ComparisonFailure: expected: but was:
>
> Stack Trace:
> org.junit.ComparisonFailure: expected: but was:
> at
> __randomizedtesting.SeedInfo.seed([6CA57EA3FB50CA0D:302BB278E1397FA3]:0)
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.lucene.index.TestParallelLeafReader.queryTest(TestParallelLeafReader.java:263)
> at
> org.apache.lucene.index.TestParallelLeafReader.testQueries(TestParallelLeafReader.java:48)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
> at
> org.apache.lucene.tests.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:48)
> at
> org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at
> org.apache.lucene.tests.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
> at
> org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
> at
> org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:843)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:490)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
> at
> org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> org.apache.lucene.tests.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
> at
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> org.apache.lucene.tests.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
> at
> org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at
> org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
> at
> org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
> at
> org.apache.lucene.tests.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:47)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.

Re: ./crave pull .. 'heapdumps/* Fwd: [JENKINS] Solr » Solr-Check-9.x - Build # 5949 - Still Failing!

2023-12-01 Thread Mikhail Khludnev 
Make sense.

On Fri, Dec 1, 2023 at 7:56 PM Yuvraaj Kelkar  wrote:

> I think the second option is what we'll go for.
> I'm going to add a flag to pull that will allow the user to specify extra
> flags to be given to rsync.
> Then we can call crave pull like this:
> ./crave pull --extra-rsync-flags ' --ignore-missing-args'
> '**/build/**/test/TEST-*.xml' '**/*.events' 'heapdumps/**' '**/hs_err_pid*'
>
>
> *** Note the additional space before the hypen in ' --ignore-missing-args'
>  .
>
> This should handle the missing source files/directories.
>
> What do you think?
>
> Thanks,
> -Uv
>
> On Dec 1 2023, at 12:56 am, Mikhail Khludnev  wrote:
>
> Hello Yuvraaj,
> Thanks for taking care of this. Honestly it's not my wheelhouse.
> I seems like there's a consideration that a test getting out of heap will
> create heapdumps folder and put a file into. I don't know wether
> test/gradle can dump heap there ever. At least we don't have tests dumps
> heap there now. So, whether this folder exists or is absent is not certain.
> We have a few options:
>  - drop heapdumps/** from crave pull until someone needs to investigate a
> test falling out of memory.
>  - hack crave pull to ignore path wildcards for absent dir
>  - execute $mkdir heapdumps or  $mkdir -p heapdumps (depending on script's
> error handling more) before $crave pull
>
>
> [image: Sent from Mailspring]
> On Thu, Nov 30, 2023 at 11:24 PM Yuvraaj Kelkar  wrote:
>
> I just started a build with crave:
> crave run ./gradlew --console=plain check integrationTests
>
> And at the end of it, looked for the patterns in the crave pull  command:
>
> admin@171074329f9e:/tmp/src/solr$ find . -name '*.events'
> admin@171074329f9e:/tmp/src/solr$ find . -name 'hs_err_pid*'
> admin@171074329f9e:/tmp/src/solr$
> admin@171074329f9e:/tmp/src/solr$ ls -l heapdumps
> ls: cannot access 'heapdumps': No such file or directory
>
>
> The only thing I could get a lot of output on was
>
> admin@171074329f9e:/tmp/src/solr$ find . | grep 'build.*test.TEST' | head
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.JsonRequestApiTest.xml
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.UsingSolrJRefGuideExamplesTest.xml
>  
> 
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.IndexingNestedDocuments.xml
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.ZkConfigFilesTest.xml
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.JsonRequestApiHeatmapFacetingTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.exporter.SolrExporterIntegrationTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.scraper.SolrStandaloneScraperBasicAuthTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.exporter.MetricsQueryTemplateTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.scraper.SolrStandaloneScraperTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.scraper.SolrCloudScraperTest.xml
>
>
> Is there some other build command required to generate the other file
> patterns?
>
> Thanks,
> -Uv
>
> On Nov 30 2023, at 11:33 am, Yuvraaj Kelkar  wrote:
>
> Investigating.
>
> On Nov 26 2023, at 12:32 am, Mikhail Khludnev  wrote:
>
> Pardon
>
> On Sun, Nov 26, 2023 at 11:28 AM Gautam Worah 
> wrote:
>
> I think you meant to send it to d...@solr.apache.org?
>
> On Sun, Nov 26, 2023 at 12:24 AM Mikhail Khludnev  wrote:
>
> Hello
> It's rather like a logical error in crave pull. How to work around it?
>
> + status=0
> + ./crave pull '**/build/**/test/TEST-*.xml' '**/*.events' 'heapdumps/**' 
> '**/hs_err_pid*'
> Error: rsync: [sender] change_dir "/tmp/src/solr/heapdumps" failed: No such 
> file or directory (2)
> rsync error: some files/attrs were not transferred (see previous errors) 
> (code 23) at main.c(1682) [Receiver=3.1.3]
> rsync: [Receiver] write error: Broken pipe (32)
>
> + exit 0
>
>
> -- Forwarded message -
> From: *Apache Jenkins Server* 
> Date: Sun, Nov 26, 2023 at 11:17 AM
> Subject: [JENKINS] Solr » Solr-Check-9.x - Build # 5949 - Still Failing!
> To: 
>
>
> Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/5949/
>
> No tests ran.
>
> Build Log:
> [...truncated 1490 lines...]
> ERROR: Step ‘Publish JUnit test result report’ failed: No test report
> files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
>

Re: ./crave pull .. 'heapdumps/* Fwd: [JENKINS] Solr » Solr-Check-9.x - Build # 5949 - Still Failing!

2023-12-01 Thread Yuvraaj Kelkar 
I think the second option is what we'll go for.
I'm going to add a flag to pull that will allow the user to specify extra flags 
to be given to rsync.
Then we can call crave pull like this:
./crave pull --extra-rsync-flags ' --ignore-missing-args' 
'**/build/**/test/TEST-*.xml' '**/*.events' 'heapdumps/**' '**/hs_err_pid*'

*** Note the additional space before the hypen in ' --ignore-missing-args' .
This should handle the missing source files/directories.
What do you think?
Thanks,
-Uv

On Dec 1 2023, at 12:56 am, Mikhail Khludnev  wrote:
> Hello Yuvraaj,
> Thanks for taking care of this. Honestly it's not my wheelhouse.
> I seems like there's a consideration that a test getting out of heap will 
> create heapdumps folder and put a file into. I don't know wether test/gradle 
> can dump heap there ever. At least we don't have tests dumps heap there now. 
> So, whether this folder exists or is absent is not certain.
> We have a few options:
> - drop heapdumps/** from crave pull until someone needs to investigate a test 
> falling out of memory.
> - hack crave pull to ignore path wildcards for absent dir
> - execute $mkdir heapdumps or $mkdir -p heapdumps (depending on script's 
> error handling more) before $crave pull
>
>
> On Thu, Nov 30, 2023 at 11:24 PM Yuvraaj Kelkar  (mailto:u...@crave.io)> wrote:
> > I just started a build with crave:
> > crave run ./gradlew --console=plain check integrationTests
> >
> > And at the end of it, looked for the patterns in the crave pull command:
> >
> > admin@171074329f9e:/tmp/src/solr$ find . -name '*.events'
> > admin@171074329f9e:/tmp/src/solr$ find . -name 'hs_err_pid*'
> > admin@171074329f9e:/tmp/src/solr$
> > admin@171074329f9e:/tmp/src/solr$ ls -l heapdumps
> > ls: cannot access 'heapdumps': No such file or directory
> >
> > The only thing I could get a lot of output on was
> >
> > admin@171074329f9e:/tmp/src/solr$ find . | grep 'build.*test.TEST' | head
> > ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.JsonRequestApiTest.xml
> > ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.UsingSolrJRefGuideExamplesTest.xml
> >  
> > (https://link.getmailspring.com/link/a1463805-bfd9-43a5-bd19-08e9ae1a4...@getmailspring.com/0?redirect=TEST-org.apache.solr.client.ref_guide_examples.UsingSolrJRefGuideExamplesTest.xml&recipient=ZGV2QGx1Y2VuZS5hcGFjaGUub3Jn)
> > ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.IndexingNestedDocuments.xml
> > ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.ZkConfigFilesTest.xml
> > ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.JsonRequestApiHeatmapFacetingTest.xml
> > ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.exporter.SolrExporterIntegrationTest.xml
> > ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.scraper.SolrStandaloneScraperBasicAuthTest.xml
> > ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.exporter.MetricsQueryTemplateTest.xml
> > ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.scraper.SolrStandaloneScraperTest.xml
> > ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.scraper.SolrCloudScraperTest.xml
> >
> > Is there some other build command required to generate the other file 
> > patterns?
> > Thanks,
> > -Uv
> >
> > On Nov 30 2023, at 11:33 am, Yuvraaj Kelkar  > (mailto:u...@crave.io)> wrote:
> > > Investigating.
> > >
> > > On Nov 26 2023, at 12:32 am, Mikhail Khludnev  > > (mailto:m...@apache.org)> wrote:
> > > > Pardon
> > > >
> > > > On Sun, Nov 26, 2023 at 11:28 AM Gautam Worah  > > > (mailto:worah.gau...@gmail.com)> wrote:
> > > > > I think you meant to send it to d...@solr.apache.org 
> > > > > (mailto:d...@solr.apache.org)?
> > > > >
> > > > > On Sun, Nov 26, 2023 at 12:24 AM Mikhail Khludnev  > > > > (mailto:m...@apache.org)> wrote:
> > > > > > Hello
> > > > > > It's rather like a logical error in crave pull. How to work around 
> > > > > > it?
> > > > > >
> > > > > > + status=0
> > > > > > + ./crave pull '**/build/**/test/TEST-*.xml' '**/*.events' 
> > > > > > 'heapdumps/**' '**/hs_err_pid*'
> > > > > > Error: rsync: [sender] change_dir "/tmp/src/solr/heapdumps" failed: 
> > > > > > No such file or directory (2)
> > > > > > rsync error: some files/attrs were not transferred (see previous 
> > > > > > errors) (code 23) at main.c(1682) [Receiver=3.1.3]
> > > > > > rsync: [Receiver] write error: Broken pipe (32)
> > > > > >
> > > > > > + exit 0
> > > > > > -- Forwarded message -
> > > > > > From: Apache Jenkins Server  > > > > > (mailto:jenk...@builds.apache.org)>
> > > > > > Date: Sun, Nov 26, 2023 at 11:17 AM
> > > > > > Subject: [JENKINS] Solr » Solr-Check-9.x - Build # 5949 - Still 
> > > > > > Failing!
> > > >

Re: [VOTE] Release Lucene 9.9.0 RC2

2023-12-01 Thread Michael McCandless 
+1


SUCCESS! [0:20:12.297376]


Mike McCandless

http://blog.mikemccandless.com


On Fri, Dec 1, 2023 at 9:21 AM Uwe Schindler  wrote:

> Hi,
>
> I let Policeman Jenkins run the smoke tester with Java 11 and Java 17
> (unfortunately we have no support for 21 yet, so new MMap and Vectors were
> not tested). But this was tested long enough, so I trust everything. I just
> did some cross-checking and validated the MR-JAR to contain all classes and
> that Javadocs are uptodate. Looks fine after the manual review.
>
> Here is Policeman's work and opinion: SUCCESS! [1:02:37.749085] (
> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/30/console)
>
> Here is my personal opinion:
> +1 to release
>
> Uwe
> Am 30.11.2023 um 18:31 schrieb Chris Hegarty:
>
> Please vote for release candidate 2 for Lucene 9.9.0
>
>
> The artifacts can be downloaded from:
>
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500
>
>
> You can run the smoke tester directly with this command:
>
>
> python3 -u dev-tools/scripts/smokeTestRelease.py \
>
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500
>
>
> The vote will be open for at least 72 hours, and given the weekend in
> between, let’s keep it open until 2023-12-04 12:00 UTC.
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
> Here is my +1
>
>
> -Chris.
>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremenhttps://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>

Re: [VOTE] Release Lucene 9.9.0 RC2

2023-12-01 Thread Uwe Schindler 

Hi,

I let Policeman Jenkins run the smoke tester with Java 11 and Java 17 
(unfortunately we have no support for 21 yet, so new MMap and Vectors 
were not tested). But this was tested long enough, so I trust 
everything. I just did some cross-checking and validated the MR-JAR to 
contain all classes and that Javadocs are uptodate. Looks fine after the 
manual review.


Here is Policeman's work and opinion: SUCCESS! [1:02:37.749085] 
(https://jenkins.thetaphi.de/job/Lucene-Release-Tester/30/console)


Here is my personal opinion:
+1 to release

Uwe

Am 30.11.2023 um 18:31 schrieb Chris Hegarty:


Please vote for release candidate 2 for Lucene 9.9.0


The artifacts can be downloaded from:

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500


You can run the smoke tester directly with this command:


python3 -u dev-tools/scripts/smokeTestRelease.py \

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500


The vote will be open for at least 72 hours, and given the weekend in 
between, let’s keep it open until 2023-12-04 12:00 UTC.


[ ] +1 approve

[ ] +0  no opinion

[ ] -1 disapprove (and reason why)


Here is my +1


-Chris.



--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de

Re: [VOTE] Release Lucene 9.9.0 RC2

2023-12-01 Thread Luca Cavanna 
SUCCESS! [0:34:53.150902]


+1


On Fri, Dec 1, 2023 at 9:06 AM Ignacio Vera  wrote:

> SUCCESS! [1:20:23.570231]
>
>
> +1
>
> On Fri, Dec 1, 2023 at 6:55 AM Shyamsunder Mutcha 
> wrote:
>
>> SUCCESS! [0:38:41.054860]
>> +1
>>
>> On Thu, Nov 30, 2023 at 9:59 PM Nhat Nguyen
>>  wrote:
>>
>>> SUCCESS! [1:22:43.808415]
>>>
>>> +1
>>>
>>> On Thu, Nov 30, 2023 at 6:09 PM Christian Moen  wrote:
>>>
 SUCCESS! [1:49:26.873909]

 +1

 On Fri, Dec 1, 2023 at 3:09 AM Chris Hegarty
  wrote:

> Please vote for release candidate 2 for Lucene 9.9.0
>
>
> The artifacts can be downloaded from:
>
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500
>
>
> You can run the smoke tester directly with this command:
>
>
> python3 -u dev-tools/scripts/smokeTestRelease.py \
>
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500
>
>
> The vote will be open for at least 72 hours, and given the weekend in
> between, let’s keep it open until 2023-12-04 12:00 UTC.
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
> Here is my +1
>
>
> -Chris.
>
>

Re: ./crave pull .. 'heapdumps/* Fwd: [JENKINS] Solr » Solr-Check-9.x - Build # 5949 - Still Failing!

2023-12-01 Thread Mikhail Khludnev 
Hello Yuvraaj,
Thanks for taking care of this. Honestly it's not my wheelhouse.
I seems like there's a consideration that a test getting out of heap will
create heapdumps folder and put a file into. I don't know wether
test/gradle can dump heap there ever. At least we don't have tests dumps
heap there now. So, whether this folder exists or is absent is not certain.
We have a few options:
 - drop heapdumps/** from crave pull until someone needs to investigate a
test falling out of memory.
 - hack crave pull to ignore path wildcards for absent dir
 - execute $mkdir heapdumps or  $mkdir -p heapdumps (depending on script's
error handling more) before $crave pull


On Thu, Nov 30, 2023 at 11:24 PM Yuvraaj Kelkar  wrote:

> I just started a build with crave:
> crave run ./gradlew --console=plain check integrationTests
>
> And at the end of it, looked for the patterns in the crave pull  command:
>
> admin@171074329f9e:/tmp/src/solr$ find . -name '*.events'
> admin@171074329f9e:/tmp/src/solr$ find . -name 'hs_err_pid*'
> admin@171074329f9e:/tmp/src/solr$
> admin@171074329f9e:/tmp/src/solr$ ls -l heapdumps
> ls: cannot access 'heapdumps': No such file or directory
>
>
> The only thing I could get a lot of output on was
>
> admin@171074329f9e:/tmp/src/solr$ find . | grep 'build.*test.TEST' | head
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.JsonRequestApiTest.xml
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.UsingSolrJRefGuideExamplesTest.xml
>  
> 
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.IndexingNestedDocuments.xml
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.ZkConfigFilesTest.xml
> ./solr/solr-ref-guide/build/test-results/test/TEST-org.apache.solr.client.ref_guide_examples.JsonRequestApiHeatmapFacetingTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.exporter.SolrExporterIntegrationTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.scraper.SolrStandaloneScraperBasicAuthTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.exporter.MetricsQueryTemplateTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.scraper.SolrStandaloneScraperTest.xml
> ./solr/prometheus-exporter/build/test-results/test/TEST-org.apache.solr.prometheus.scraper.SolrCloudScraperTest.xml
>
>
> Is there some other build command required to generate the other file
> patterns?
>
> Thanks,
> -Uv
>
> On Nov 30 2023, at 11:33 am, Yuvraaj Kelkar  wrote:
>
> Investigating.
>
> On Nov 26 2023, at 12:32 am, Mikhail Khludnev  wrote:
>
> Pardon
>
> [image: Sent from Mailspring]
> On Sun, Nov 26, 2023 at 11:28 AM Gautam Worah 
> wrote:
>
> I think you meant to send it to d...@solr.apache.org?
>
> On Sun, Nov 26, 2023 at 12:24 AM Mikhail Khludnev  wrote:
>
> Hello
> It's rather like a logical error in crave pull. How to work around it?
>
> + status=0
> + ./crave pull '**/build/**/test/TEST-*.xml' '**/*.events' 'heapdumps/**' 
> '**/hs_err_pid*'
> Error: rsync: [sender] change_dir "/tmp/src/solr/heapdumps" failed: No such 
> file or directory (2)
> rsync error: some files/attrs were not transferred (see previous errors) 
> (code 23) at main.c(1682) [Receiver=3.1.3]
> rsync: [Receiver] write error: Broken pipe (32)
>
> + exit 0
>
>
> -- Forwarded message -
> From: *Apache Jenkins Server* 
> Date: Sun, Nov 26, 2023 at 11:17 AM
> Subject: [JENKINS] Solr » Solr-Check-9.x - Build # 5949 - Still Failing!
> To: 
>
>
> Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/5949/
>
> No tests ran.
>
> Build Log:
> [...truncated 1490 lines...]
> ERROR: Step ‘Publish JUnit test result report’ failed: No test report
> files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> -
> To unsubscribe, e-mail: builds-unsubscr...@solr.apache.org
> For additional commands, e-mail: builds-h...@solr.apache.org
>
>
> --
> Sincerely yours
> Mikhail Khludnev
>
>
>
> --
> Sincerely yours
> Mikhail Khludnev
>
>

-- 
Sincerely yours
Mikhail Khludnev

Re: [VOTE] Release Lucene 9.9.0 RC2

2023-12-01 Thread Ignacio Vera 
SUCCESS! [1:20:23.570231]


+1

On Fri, Dec 1, 2023 at 6:55 AM Shyamsunder Mutcha  wrote:

> SUCCESS! [0:38:41.054860]
> +1
>
> On Thu, Nov 30, 2023 at 9:59 PM Nhat Nguyen 
> wrote:
>
>> SUCCESS! [1:22:43.808415]
>>
>> +1
>>
>> On Thu, Nov 30, 2023 at 6:09 PM Christian Moen  wrote:
>>
>>> SUCCESS! [1:49:26.873909]
>>>
>>> +1
>>>
>>> On Fri, Dec 1, 2023 at 3:09 AM Chris Hegarty
>>>  wrote:
>>>
 Please vote for release candidate 2 for Lucene 9.9.0


 The artifacts can be downloaded from:


 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500


 You can run the smoke tester directly with this command:


 python3 -u dev-tools/scripts/smokeTestRelease.py \


 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500


 The vote will be open for at least 72 hours, and given the weekend in
 between, let’s keep it open until 2023-12-04 12:00 UTC.

 [ ] +1  approve

 [ ] +0  no opinion

 [ ] -1  disapprove (and reason why)


 Here is my +1


 -Chris.