On 23 Nov 2016, at 14:30, Dmitry Timoshkov dmitry@baikal.ru wrote:
Huw Davies huw@codeweavers.com wrote:
There should be a better way of detecting broken behaviour then, in current form the failures just get hidden under a broken() blanket, effectively disabling the whole test, and making it useless. Perhaps something like the check for ntdll exports that's performed at the start of the test.
I don’t see why this case is any different from other similar broken behaviours. Note that under Wine, broken is inverted, so the test is not ‘disabled' on that platform.
I'm more concerned about testing Windows behaviour, and staying compatible enough. Apparently Microsoft has changed some internal bits how window procs get the A/W affinity (and DefWindowProcA/W in particular), and I would like to know the reason of the test breakage. Disabling the test by marking its result as broken is usually the last resort thing after a clear understanding what is going on.
The reason for the test breakage is because Microsoft changed some internal bits on how window procs get the A/W affinity… And made a mess of it while doing so.
Another option is to just remove this test.
Huw.