Hi, I think that's a bug in the test that should be fixed. In the past we had some extra check about "release branches" in it, which seems to no longer work.
IMHO, one a release is done, the release branch should switch to the next version asap. -1 to revert the changes in branch_6_6 Uwe ----- Uwe Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Steve Rowe [mailto:[email protected]] > Sent: Thursday, March 1, 2018 7:24 PM > To: Lucene Dev <[email protected]> > Subject: Re: Tests failing over the last day or so > > > > On Mar 1, 2018, at 12:34 PM, Erick Erickson <[email protected]> > wrote: > > Missing backcompat test files: 6.6.3-cfs 7.2.1-cfs: > > > org.apache.lucene.index.TestBackwardsCompatibility.testAllVersionsTested > > I caused this by running addVersion.py for 6.6.3 on branch_6_6, branch_6x, > branch_7x, and master and then committing and pushing the changes (that’s > what ReleaseToDo says to do). Not sure why 7.2.1-cfs is on ^^ that list, > probably (just) a reporting bug (since index.7.2.1-cfs.zip is present). I’ll > revert for now on non-release branches, and modify the ReleaseToDo to > delay addVersion.py on non-release branches, to be run as a post-release > task. > > -- > Steve > www.lucidworks.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
