Re: @TimeoutSuite and defaults (RandomizedTesting)

2024-02-12 Thread Dawid Weiss
You can override the defaults using sysprops in your CI builds -

-Ptests.timeoutSuite=1000!

takes precedence over any annotations (1 second).

Dawid

On Mon, Feb 12, 2024 at 7:53 PM David Smiley  wrote:

> Looking at LuceneTestCase, I see the annotation from RandomizedTesting:
> @TimeoutSuite(millis = 2 * TimeUnits.HOUR)
> This matches my observations of some builds that timed out, perhaps
> some flaky test hanging in Solr (that extends LuceneTestCase).
> Looking at this annotation, there is further documentation that the
> default can be set via sysprop tests.timeoutSuite.  Wouldn't doing
> that make more sense than hard-coding this figure in LuceneTestCase?
> For example, I'd like to have a normal/default test run have a low
> timeout (10min?) but on a "nightly" run on CI, use much higher.  Not 2
> hours though; individual tests needing so much should have a
> TimeoutSuite applied to them.
>
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>


@TimeoutSuite and defaults (RandomizedTesting)

2024-02-12 Thread David Smiley
Looking at LuceneTestCase, I see the annotation from RandomizedTesting:
@TimeoutSuite(millis = 2 * TimeUnits.HOUR)
This matches my observations of some builds that timed out, perhaps
some flaky test hanging in Solr (that extends LuceneTestCase).
Looking at this annotation, there is further documentation that the
default can be set via sysprop tests.timeoutSuite.  Wouldn't doing
that make more sense than hard-coding this figure in LuceneTestCase?
For example, I'd like to have a normal/default test run have a low
timeout (10min?) but on a "nightly" run on CI, use much higher.  Not 2
hours though; individual tests needing so much should have a
TimeoutSuite applied to them.

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: (lucene) branch branch_9_10 created (now 695c0ac8450)

2024-02-12 Thread Adrien Grand
You're so quick Uwe, thank you!

On Mon, Feb 12, 2024 at 2:49 PM Uwe Schindler  wrote:

> Hi Adrien,
>
> Thanks for creating the branch. I activated Policeman Jenkins tests for it.
>
> Uwe
>
> Am 12.02.2024 um 14:30 schrieb jpou...@apache.org:
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > jpountz pushed a change to branch branch_9_10
> > in repository https://gitbox.apache.org/repos/asf/lucene.git
> >
> >
> >at 695c0ac8450 Add the missing Version field for 8.11.3. (#13093)
> >
> > No new revisions were added by this update.
> >
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

-- 
Adrien


New branch and feature freeze for Lucene 9.10.0

2024-02-12 Thread Adrien Grand
NOTICE:

Branch branch_9_10 has been cut and versions updated to 9.11 on stable
branch.

Please observe the normal rules:

* No new features may be committed to the branch.
* Documentation patches, build patches and serious bug fixes may be
  committed to the branch. However, you should submit all patches you
  want to commit as pull requests first to give others the chance to review
  and possibly vote against them. Keep in mind that it is our
  main intention to keep the branch as stable as possible.
* All patches that are intended for the branch should first be committed
  to the unstable branch, merged into the stable branch, and then into
  the current release branch.
* Normal unstable and stable branch development may continue as usual.
  However, if you plan to commit a big change to the unstable branch
  while the branch feature freeze is in effect, think twice: can't the
  addition wait a couple more days? Merges of bug fixes into the branch
  may become more difficult.
* Only Github issues with Milestone 9.10
  and priority "Blocker" will delay a release candidate build.

We have one such blocker currently:
https://github.com/apache/lucene/issues/13094.

-- 
Adrien


Re: (lucene) branch branch_9_10 created (now 695c0ac8450)

2024-02-12 Thread Uwe Schindler

Hi Adrien,

Thanks for creating the branch. I activated Policeman Jenkins tests for it.

Uwe

Am 12.02.2024 um 14:30 schrieb jpou...@apache.org:

This is an automated email from the ASF dual-hosted git repository.

jpountz pushed a change to branch branch_9_10
in repository https://gitbox.apache.org/repos/asf/lucene.git


   at 695c0ac8450 Add the missing Version field for 8.11.3. (#13093)

No new revisions were added by this update.


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


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org