On Sun, Nov 01, 2015 at 09:14:53PM +0100, Kornel Benko wrote: > Am Sonntag, 1. November 2015 um 19:37:41, schrieb Guenter Milde > <mi...@users.sf.net> > > On 2015-10-30, Kornel Benko wrote:
> > Solving all issues that arise from this combination is diverting attention > > and ressources from more important tasks. > > Most of these tests were working some time ago. We already have many inverted > test. > I am strongly against such policy. First one has to check if the reason is > really > babel/polyglossia conflict. I agree that we should check before reverting. Actually I don't think babel/polyglossia plays a role in most of the failing tests. There are only a few that fail because of this (you can see this by reverting the polyglossia commit, edd37de8). Georg has already done a good job of improving things and only a few affected tests remain. The main issue is the missing characters commit, I think. And this is a tricky issue because the commit that broke the tests was actually a good commit---it did not introduce a bug. What to do in such a case? I'm not sure. Ideally we would have a separate branch where we try to address the tests (either fixing the underlying bugs or fixing the .lyx files or inverting the tests). This way the tests on master continue to be clean and it is easy to see if there are any regressions. But I fear this is too much of an inconvenience to people who already are annoyed by the tests. > > Also, we identified some generic problems with this combination that are > > not solvable in the short term: third party packages well as documents > > not prepared for this use case. > > > > Just reverting failing Xetex export tests for the moment would allow us to > > concentrfate on the remaining failing test and get the test suite in a > > usable state again. > > Optimist (I mean 'usable state'). > I am strongly against such policy. First one has to check if the reason is > really > babel/polyglossia conflict. > There are already too many tests inverted, no one cares anymore. Actually the last few weeks have seen the most interest in the tests yet. Other developers are trying to run the tests, which is already an improvement. I would say this is the height of interest in the export tests :) Scott
