A couple days ago I configured Crave via adding to gradle.properties:
tests.timeoutSuite=60!
That's 10 minutes. In Jenkins, it should be longer, maybe 20.
This could be passed in the CLI with "-P". The trailing exclamation
is an override over that of LuceneTestCase, which I'm arguing in
Does anyone know how to do this? I have never touched the Jenkins jobs…
On Tue, Jan 23, 2024 at 11:50 AM David Smiley wrote:
> Please configure it to stop the build after a couple hours. We never
> want a build running for longer.
>
> On Mon, Jan 22, 2024 at 7:53 AM Eric Pugh wrote:
> >
> >
Please configure it to stop the build after a couple hours. We never
want a build running for longer.
On Mon, Jan 22, 2024 at 7:53 AM Eric Pugh wrote:
>
> Build https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/168/ has been
> running for five days! Guessing it's not going to finish.
Build https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/168/ has been
running for five days! Guessing it's not going to finish.
I clicked the "Stop" button on the build and will see what happens. I might
let it run another time to see if the test starts behaving, and if not, then
Okay, I checked and it looks like the test failed, and is causing the entire
build to hang...
https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/168/console
The test runs on my local machine just fineAnd it appears to be running
just fine on Solr-Check-main.
Is there a way
I will take a look….
> On Jan 17, 2024, at 10:38 AM, David Smiley wrote:
>
> The integration tests (bats) are failing on branch_9x for me locally and as
> also seen in Jenkins.
>> not ok 3 auth enable/disable lifecycle in 1ms
>
The integration tests (bats) are failing on branch_9x for me locally and as
also seen in Jenkins.
> not ok 3 auth enable/disable lifecycle in 1ms
https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/167/console
Hopefully someone has a clue why?
~ David Smiley
Apache Lucene/Solr
