[
https://issues.apache.org/jira/browse/LUCENE-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-5863:
---------------------------------------
Attachment: testTheBWCTester.py
Here's a start at a simple tool to "test the tester". It loads all known
releases from http://archive.apache.org/dist/lucene/java, then it runs both
back-compat tests with verbose and watches which indices they said they tested,
and does a delta of the two sets.
Curiously it discovered 1.9.0 is tested but not released (I think maybe that
release was pulled after a serious bug... vague memories).
But then it current fails with this output:
{noformat}
Releases that don't seem to be tested:
1.4.3
1.9.1
2.3.1
2.3.2
2.4.1
2.9.1
2.9.2
2.9.3
2.9.4
4.0.0.0
4.0.0.1
4.2.1
4.3.0
4.3.1
4.4.0
4.5.1
4.6.0
4.7.0
4.7.1
4.7.2
{noformat}
I keep svn up'ing after Rob commits a new index (thanks Rob!) and the list
shrinks :)
> Generate backwards compatibility indexes for all 4.x releases
> -------------------------------------------------------------
>
> Key: LUCENE-5863
> URL: https://issues.apache.org/jira/browse/LUCENE-5863
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Attachments: testTheBWCTester.py
>
>
> Currently the versioning here is a total mess, and its inconsistent across
> bugfix releases.
> We should just generate back compat indexes for every release: regardless of
> whether the index format changed, even for bugfix releases. This ensures at
> least we try to test that the back compat is working.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
