http://bugs.winehq.org/show_bug.cgi?id=21773
--- Comment #13 from Ian Goddard iang@austonley.org.uk 2010-02-27 07:54:42 --- (In reply to comment #12)
(In reply to comment #11)
(In reply to comment #10) Just read your last sentence again: "Of course in all cases you have to start with clean wineprefix and make sure wine_gecko is available."
If you simply tell people to take any of the above 3 you do not assure that the proviso in that sentence will be met. That means that you cannot trust any of the regression-testing results you get back from the community.
Simply using the wine from the current source tree isn't enough. Good testing practice just isn't that simple.
The goal of the tests is not to run against an ideal perfect setup that is always identical. Getting a variety of tests run against a variety of setups, some less correct than others, is much more useful for spotting problems.
I understand that, at least as regards a variety of H/W and O/S platforms and the test system reports such platform details back to you.
However, as I understand it, if $WINEPREFIX were not clean but pointed to the current, older, production installation the test could wander off and pick up dlls from that installation. If that happens the results reported back to you would largely reflect that version. In a production installation such as mine you'd be seeing the results of a patched winex11.drv. It may be that you're seeing more variety than you think!
Ian