[1/4] user32/tests: remove WM_DESTROY processing in test (it is of no use and causes tests skipping) (try 2)

[Marvin]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=18723

Your paranoid android.


=== W7PROX64 (32 bit dialog) ===
dialog.c:1370: Test failed: Dialog should not be visible.

=== TEST64_W7SP1 (32 bit dialog) ===
dialog.c:1370: Test failed: Dialog should not be visible.

=== W7PROX64 (64 bit dialog) ===
dialog.c:1370: Test failed: Dialog should not be visible.

=== TEST64_W7SP1 (64 bit dialog) ===
dialog.c:1370: Test failed: Dialog should not be visible.