You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@solr.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2025/10/10 18:57:46 UTC
[JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Build: https://ci-builds.apache.org/job/Solr/job/Solr-Lint-main/334/
No tests ran.
Build Log:
[...truncated 1184 lines...]
BUILD FAILED in 10m 43s
638 actionable tasks: 638 executed
Publishing build scan...
https://develocity.apache.org/s/bfc7jlfyzxtks
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
[JENKINS] Solr » Solr-Lint-main - Build # 336 - Still Failing!
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Build: https://ci-builds.apache.org/job/Solr/job/Solr-Lint-main/336/
No tests ran.
Build Log:
[...truncated 1184 lines...]
BUILD FAILED in 10m 20s
638 actionable tasks: 638 executed
Publishing build scan...
https://develocity.apache.org/s/urcpcmpqsijsu
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
[JENKINS] Solr » Solr-Lint-main - Build # 335 - Still Failing!
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Build: https://ci-builds.apache.org/job/Solr/job/Solr-Lint-main/335/
No tests ran.
Build Log:
[...truncated 1184 lines...]
BUILD FAILED in 10m 51s
638 actionable tasks: 638 executed
Publishing build scan...
https://develocity.apache.org/s/ttynco45mnaky
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Ishan Chattopadhyaya <ic...@gmail.com>.
I've disabled the test for now. If this doesn't fix the builds, I'll revert
the whole module.
On Sat, 11 Oct 2025 at 01:22, Ishan Chattopadhyaya <
ichattopadhyaya@gmail.com> wrote:
> In the Jenkins boxes, we run something like the following:
>
> [Solr-Test-main] $ /home/jenkins/jenkins-agent/workspace/Solr/Solr-Test-main/gradlew -Dtests.haltonfailure=false -Dtests.badapples=false --continue test
>
>
> One idea is to disable (@Ignore) all the cuVS tests immediately, and once
> the official cuVS-java artifacts are released via maven central, we run the
> above job with a "--refresh-dependencies" param to unpoison the checksum
> caches.
>
> Hoss, WDYT ^ ?
>
> On Sat, 11 Oct 2025 at 00:58, Ishan Chattopadhyaya <
> ichattopadhyaya@gmail.com> wrote:
>
>> @Vivek Narang <vi...@gmail.com> FYI, in case you're not
>> subscribed to the list. Any ideas, please?
>>
>> On Sat, 11 Oct, 2025, 12:57 am Ishan Chattopadhyaya, <
>> ichattopadhyaya@gmail.com> wrote:
>>
>>> I'm now wondering how to ever fix this situation..
>>>
>>> Maybe, only when 25.10.1 (may or may not even happen) or 25.12.0
>>> (December release) is released can this be fixed? I'm out of ideas. I guess
>>> these machines are now poisoned with those stale checksums.
>>>
>>> I now feel, in hindsight, that I should've fixed that strict version
>>> checking thing in cuVS and released differently versioned artifacts for
>>> snapshots. But, it is too late now.
>>>
>>> On Sat, 11 Oct, 2025, 12:44 am Chris Hostetter, <
>>> hossman_lucene@fucit.org> wrote:
>>>
>>>>
>>>> https://issues.apache.org/jira/browse/SOLR-17917
>>>>
>>>> FYI: Most of the jenkins "main" builds are now failing because they
>>>> have
>>>> the "old" cuvs 25.10.0 jars in their gradle caches and main has been
>>>> upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
>>>> jars)
>>>>
>>>> So they either run tests and fail with something like...
>>>>
>>>> java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
>>>> com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
>>>> public no-arg constructor
>>>>
>>>> ..or in the case of the "lint" jobs, that skip tests, they fail because
>>>> the checksum in their cache doesn't match the checksum committed by
>>>> https://github.com/apache/solr/pull/3731
>>>>
>>>>
>>>>
>>>> -Hoss
>>>> http://www.lucidworks.com/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
>>>> For additional commands, e-mail: dev-help@solr.apache.org
>>>>
>>>>
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Ishan Chattopadhyaya <ic...@gmail.com>.
I've disabled the test for now. If this doesn't fix the builds, I'll revert
the whole module.
On Sat, 11 Oct 2025 at 01:22, Ishan Chattopadhyaya <
ichattopadhyaya@gmail.com> wrote:
> In the Jenkins boxes, we run something like the following:
>
> [Solr-Test-main] $ /home/jenkins/jenkins-agent/workspace/Solr/Solr-Test-main/gradlew -Dtests.haltonfailure=false -Dtests.badapples=false --continue test
>
>
> One idea is to disable (@Ignore) all the cuVS tests immediately, and once
> the official cuVS-java artifacts are released via maven central, we run the
> above job with a "--refresh-dependencies" param to unpoison the checksum
> caches.
>
> Hoss, WDYT ^ ?
>
> On Sat, 11 Oct 2025 at 00:58, Ishan Chattopadhyaya <
> ichattopadhyaya@gmail.com> wrote:
>
>> @Vivek Narang <vi...@gmail.com> FYI, in case you're not
>> subscribed to the list. Any ideas, please?
>>
>> On Sat, 11 Oct, 2025, 12:57 am Ishan Chattopadhyaya, <
>> ichattopadhyaya@gmail.com> wrote:
>>
>>> I'm now wondering how to ever fix this situation..
>>>
>>> Maybe, only when 25.10.1 (may or may not even happen) or 25.12.0
>>> (December release) is released can this be fixed? I'm out of ideas. I guess
>>> these machines are now poisoned with those stale checksums.
>>>
>>> I now feel, in hindsight, that I should've fixed that strict version
>>> checking thing in cuVS and released differently versioned artifacts for
>>> snapshots. But, it is too late now.
>>>
>>> On Sat, 11 Oct, 2025, 12:44 am Chris Hostetter, <
>>> hossman_lucene@fucit.org> wrote:
>>>
>>>>
>>>> https://issues.apache.org/jira/browse/SOLR-17917
>>>>
>>>> FYI: Most of the jenkins "main" builds are now failing because they
>>>> have
>>>> the "old" cuvs 25.10.0 jars in their gradle caches and main has been
>>>> upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
>>>> jars)
>>>>
>>>> So they either run tests and fail with something like...
>>>>
>>>> java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
>>>> com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
>>>> public no-arg constructor
>>>>
>>>> ..or in the case of the "lint" jobs, that skip tests, they fail because
>>>> the checksum in their cache doesn't match the checksum committed by
>>>> https://github.com/apache/solr/pull/3731
>>>>
>>>>
>>>>
>>>> -Hoss
>>>> http://www.lucidworks.com/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
>>>> For additional commands, e-mail: dev-help@solr.apache.org
>>>>
>>>>
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Ishan Chattopadhyaya <ic...@gmail.com>.
In the Jenkins boxes, we run something like the following:
[Solr-Test-main] $
/home/jenkins/jenkins-agent/workspace/Solr/Solr-Test-main/gradlew
-Dtests.haltonfailure=false -Dtests.badapples=false --continue test
One idea is to disable (@Ignore) all the cuVS tests immediately, and once
the official cuVS-java artifacts are released via maven central, we run the
above job with a "--refresh-dependencies" param to unpoison the checksum
caches.
Hoss, WDYT ^ ?
On Sat, 11 Oct 2025 at 00:58, Ishan Chattopadhyaya <
ichattopadhyaya@gmail.com> wrote:
> @Vivek Narang <vi...@gmail.com> FYI, in case you're not
> subscribed to the list. Any ideas, please?
>
> On Sat, 11 Oct, 2025, 12:57 am Ishan Chattopadhyaya, <
> ichattopadhyaya@gmail.com> wrote:
>
>> I'm now wondering how to ever fix this situation..
>>
>> Maybe, only when 25.10.1 (may or may not even happen) or 25.12.0
>> (December release) is released can this be fixed? I'm out of ideas. I guess
>> these machines are now poisoned with those stale checksums.
>>
>> I now feel, in hindsight, that I should've fixed that strict version
>> checking thing in cuVS and released differently versioned artifacts for
>> snapshots. But, it is too late now.
>>
>> On Sat, 11 Oct, 2025, 12:44 am Chris Hostetter, <ho...@fucit.org>
>> wrote:
>>
>>>
>>> https://issues.apache.org/jira/browse/SOLR-17917
>>>
>>> FYI: Most of the jenkins "main" builds are now failing because they have
>>> the "old" cuvs 25.10.0 jars in their gradle caches and main has been
>>> upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
>>> jars)
>>>
>>> So they either run tests and fail with something like...
>>>
>>> java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
>>> com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
>>> public no-arg constructor
>>>
>>> ..or in the case of the "lint" jobs, that skip tests, they fail because
>>> the checksum in their cache doesn't match the checksum committed by
>>> https://github.com/apache/solr/pull/3731
>>>
>>>
>>>
>>> -Hoss
>>> http://www.lucidworks.com/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
>>> For additional commands, e-mail: dev-help@solr.apache.org
>>>
>>>
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Ishan Chattopadhyaya <ic...@gmail.com>.
In the Jenkins boxes, we run something like the following:
[Solr-Test-main] $
/home/jenkins/jenkins-agent/workspace/Solr/Solr-Test-main/gradlew
-Dtests.haltonfailure=false -Dtests.badapples=false --continue test
One idea is to disable (@Ignore) all the cuVS tests immediately, and once
the official cuVS-java artifacts are released via maven central, we run the
above job with a "--refresh-dependencies" param to unpoison the checksum
caches.
Hoss, WDYT ^ ?
On Sat, 11 Oct 2025 at 00:58, Ishan Chattopadhyaya <
ichattopadhyaya@gmail.com> wrote:
> @Vivek Narang <vi...@gmail.com> FYI, in case you're not
> subscribed to the list. Any ideas, please?
>
> On Sat, 11 Oct, 2025, 12:57 am Ishan Chattopadhyaya, <
> ichattopadhyaya@gmail.com> wrote:
>
>> I'm now wondering how to ever fix this situation..
>>
>> Maybe, only when 25.10.1 (may or may not even happen) or 25.12.0
>> (December release) is released can this be fixed? I'm out of ideas. I guess
>> these machines are now poisoned with those stale checksums.
>>
>> I now feel, in hindsight, that I should've fixed that strict version
>> checking thing in cuVS and released differently versioned artifacts for
>> snapshots. But, it is too late now.
>>
>> On Sat, 11 Oct, 2025, 12:44 am Chris Hostetter, <ho...@fucit.org>
>> wrote:
>>
>>>
>>> https://issues.apache.org/jira/browse/SOLR-17917
>>>
>>> FYI: Most of the jenkins "main" builds are now failing because they have
>>> the "old" cuvs 25.10.0 jars in their gradle caches and main has been
>>> upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
>>> jars)
>>>
>>> So they either run tests and fail with something like...
>>>
>>> java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
>>> com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
>>> public no-arg constructor
>>>
>>> ..or in the case of the "lint" jobs, that skip tests, they fail because
>>> the checksum in their cache doesn't match the checksum committed by
>>> https://github.com/apache/solr/pull/3731
>>>
>>>
>>>
>>> -Hoss
>>> http://www.lucidworks.com/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
>>> For additional commands, e-mail: dev-help@solr.apache.org
>>>
>>>
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Ishan Chattopadhyaya <ic...@gmail.com>.
@Vivek Narang <vi...@gmail.com> FYI, in case you're not
subscribed to the list. Any ideas, please?
On Sat, 11 Oct, 2025, 12:57 am Ishan Chattopadhyaya, <
ichattopadhyaya@gmail.com> wrote:
> I'm now wondering how to ever fix this situation..
>
> Maybe, only when 25.10.1 (may or may not even happen) or 25.12.0 (December
> release) is released can this be fixed? I'm out of ideas. I guess these
> machines are now poisoned with those stale checksums.
>
> I now feel, in hindsight, that I should've fixed that strict version
> checking thing in cuVS and released differently versioned artifacts for
> snapshots. But, it is too late now.
>
> On Sat, 11 Oct, 2025, 12:44 am Chris Hostetter, <ho...@fucit.org>
> wrote:
>
>>
>> https://issues.apache.org/jira/browse/SOLR-17917
>>
>> FYI: Most of the jenkins "main" builds are now failing because they have
>> the "old" cuvs 25.10.0 jars in their gradle caches and main has been
>> upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
>> jars)
>>
>> So they either run tests and fail with something like...
>>
>> java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
>> com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
>> public no-arg constructor
>>
>> ..or in the case of the "lint" jobs, that skip tests, they fail because
>> the checksum in their cache doesn't match the checksum committed by
>> https://github.com/apache/solr/pull/3731
>>
>>
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
>> For additional commands, e-mail: dev-help@solr.apache.org
>>
>>
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Ishan Chattopadhyaya <ic...@gmail.com>.
@Vivek Narang <vi...@gmail.com> FYI, in case you're not
subscribed to the list. Any ideas, please?
On Sat, 11 Oct, 2025, 12:57 am Ishan Chattopadhyaya, <
ichattopadhyaya@gmail.com> wrote:
> I'm now wondering how to ever fix this situation..
>
> Maybe, only when 25.10.1 (may or may not even happen) or 25.12.0 (December
> release) is released can this be fixed? I'm out of ideas. I guess these
> machines are now poisoned with those stale checksums.
>
> I now feel, in hindsight, that I should've fixed that strict version
> checking thing in cuVS and released differently versioned artifacts for
> snapshots. But, it is too late now.
>
> On Sat, 11 Oct, 2025, 12:44 am Chris Hostetter, <ho...@fucit.org>
> wrote:
>
>>
>> https://issues.apache.org/jira/browse/SOLR-17917
>>
>> FYI: Most of the jenkins "main" builds are now failing because they have
>> the "old" cuvs 25.10.0 jars in their gradle caches and main has been
>> upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
>> jars)
>>
>> So they either run tests and fail with something like...
>>
>> java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
>> com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
>> public no-arg constructor
>>
>> ..or in the case of the "lint" jobs, that skip tests, they fail because
>> the checksum in their cache doesn't match the checksum committed by
>> https://github.com/apache/solr/pull/3731
>>
>>
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
>> For additional commands, e-mail: dev-help@solr.apache.org
>>
>>
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Ishan Chattopadhyaya <ic...@gmail.com>.
I'm now wondering how to ever fix this situation..
Maybe, only when 25.10.1 (may or may not even happen) or 25.12.0 (December
release) is released can this be fixed? I'm out of ideas. I guess these
machines are now poisoned with those stale checksums.
I now feel, in hindsight, that I should've fixed that strict version
checking thing in cuVS and released differently versioned artifacts for
snapshots. But, it is too late now.
On Sat, 11 Oct, 2025, 12:44 am Chris Hostetter, <ho...@fucit.org>
wrote:
>
> https://issues.apache.org/jira/browse/SOLR-17917
>
> FYI: Most of the jenkins "main" builds are now failing because they have
> the "old" cuvs 25.10.0 jars in their gradle caches and main has been
> upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
> jars)
>
> So they either run tests and fail with something like...
>
> java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
> com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
> public no-arg constructor
>
> ..or in the case of the "lint" jobs, that skip tests, they fail because
> the checksum in their cache doesn't match the checksum committed by
> https://github.com/apache/solr/pull/3731
>
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
> For additional commands, e-mail: dev-help@solr.apache.org
>
>
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Ishan Chattopadhyaya <ic...@gmail.com>.
I'm now wondering how to ever fix this situation..
Maybe, only when 25.10.1 (may or may not even happen) or 25.12.0 (December
release) is released can this be fixed? I'm out of ideas. I guess these
machines are now poisoned with those stale checksums.
I now feel, in hindsight, that I should've fixed that strict version
checking thing in cuVS and released differently versioned artifacts for
snapshots. But, it is too late now.
On Sat, 11 Oct, 2025, 12:44 am Chris Hostetter, <ho...@fucit.org>
wrote:
>
> https://issues.apache.org/jira/browse/SOLR-17917
>
> FYI: Most of the jenkins "main" builds are now failing because they have
> the "old" cuvs 25.10.0 jars in their gradle caches and main has been
> upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
> jars)
>
> So they either run tests and fail with something like...
>
> java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
> com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
> public no-arg constructor
>
> ..or in the case of the "lint" jobs, that skip tests, they fail because
> the checksum in their cache doesn't match the checksum committed by
> https://github.com/apache/solr/pull/3731
>
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
> For additional commands, e-mail: dev-help@solr.apache.org
>
>
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Chris Hostetter <ho...@fucit.org>.
https://issues.apache.org/jira/browse/SOLR-17917
FYI: Most of the jenkins "main" builds are now failing because they have
the "old" cuvs 25.10.0 jars in their gradle caches and main has been
upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
jars)
So they either run tests and fail with something like...
java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
public no-arg constructor
..or in the case of the "lint" jobs, that skip tests, they fail because
the checksum in their cache doesn't match the checksum committed by
https://github.com/apache/solr/pull/3731
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
For additional commands, e-mail: dev-help@solr.apache.org
Re: [JENKINS] Solr » Solr-Lint-main - Build # 334 - Still Failing!
Posted by Chris Hostetter <ho...@fucit.org>.
https://issues.apache.org/jira/browse/SOLR-17917
FYI: Most of the jenkins "main" builds are now failing because they have
the "old" cuvs 25.10.0 jars in their gradle caches and main has been
upgraded to Lucene 10.3 (which only works with the "new" cuvs 25.10.0
jars)
So they either run tests and fail with something like...
java.util.ServiceConfigurationError: org.apache.lucene.codecs.Codec:
com.nvidia.cuvs.lucene.Lucene101AcceleratedHNSWCodec Unable to get
public no-arg constructor
..or in the case of the "lint" jobs, that skip tests, they fail because
the checksum in their cache doesn't match the checksum committed by
https://github.com/apache/solr/pull/3731
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@solr.apache.org
For additional commands, e-mail: builds-help@solr.apache.org