"Dmitry Timoshkov" dmitry@codeweavers.com writes:
It would be better, yes, but I don't see how adding new tests could avoid that if the existing test fail already. I don't see how I can make existing tests not fail while adding new ones and not touching any real code. I can resend the patch with omitting the lines in my patch which mark existing (failing) tests as todo, is that what you need? Certaily I can have a look why existing tests fail (do they fail for you?), but that has nothing to do with this my patch.
No, the existing tests don't fail for me, otherwise they wouldn't be in the tree.