You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Michael Sokolov (Jira)" <ji...@apache.org> on 2021/10/12 12:57:00 UTC
[jira] [Comment Edited] (LUCENE-10168) drop support for 7.0 indexes
in 9.0 (master)
[ https://issues.apache.org/jira/browse/LUCENE-10168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427664#comment-17427664 ]
Michael Sokolov edited comment on LUCENE-10168 at 10/12/21, 12:56 PM:
----------------------------------------------------------------------
I haven't messed around with these tests, so I was curious and did some timing with curious results; I think you mean the tests in backward-codecs? My laptop runs tests in backward-codecs (2 runs) in 2m16s/2m22s in IntelliJ and 43s/43s running {{./gradlew lucene:backward-codecs:test}}. Hunh? Is gradle caching some test results? When I run all tests using gradle, it takes 6m21s/6m44s - I don't see a way to run all tests from IntelliJ. If it's true that backward-codecs tests take 43s, or about 1/18 of the total, then this doesn't seem like such a big deal, but I'm not sure about the measurement here.
Assuming I'm wrong and there is a lot of time dedicated to testing back-compat (are there tests outside backward-codecs that also do that?), what about running them less often: making them {{@Nightly}} tests?
was (Author: sokolov):
I haven't messed around with these tests, so I was curious and did some timing with curious results; I think you mean the tests in backward-codecs? My laptop runs tests in backward-codecs (2 runs) in 2m16s/2m22s in IntelliJ and 43s/43s running {{./gradlew lucene:backward-codecs:test }}. Hunh? Is gradle caching some test results? When I run all tests using gradle, it takes 6m21s/6m44s - I don't see a way to run all tests from IntelliJ. If it's true that backward-codecs tests take 43s, or about 1/18 of the total, then this doesn't seem like such a big deal, but I'm not sure about the measurement here.
Assuming I'm wrong and there is a lot of time dedicated to testing back-compat (are there tests outside backward-codecs that also do that?), what about running them less often: making them @Nightly tests?
> drop support for 7.0 indexes in 9.0 (master)
> --------------------------------------------
>
> Key: LUCENE-10168
> URL: https://issues.apache.org/jira/browse/LUCENE-10168
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Blocker
>
> Recently it was decided to extend back compat *two* major releases, as a best effort.
> The effort has not been the best, though.
> Test times have doubled (10 minutes vs 5 minutes on my computer), all the slowness is in backwards codecs tests. And 9.0 isn't even released! Imagine how slow the tests would be if we somehow made it to e.g. 9.10 release or something.
> It is unsustainable.
> This issue is to drop support for 7.0 indexes. I realize some ppl won't be happy about that, if you don't like it, then suggest some alternative fix for the tests and put in your time. Otherwise bye bye.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org