Re: [v3 09/12] comctl32: TaskDialog - Changed tests to allow sending messages

[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
https://testbot.winehq.org/JobDetails.pl?Key=29422

Your paranoid android.


=== wvistau64 (64 bit taskdialog) ===
comctl32:taskdialog returned an error (3221226356) despite having no failures
comctl32:taskdialog has no test summary line (early exit of the main process?)

=== w2008s64 (64 bit taskdialog) ===
comctl32:taskdialog returned an error (3221226356) despite having no failures
comctl32:taskdialog has no test summary line (early exit of the main process?)

=== w7pro64 (64 bit taskdialog) ===
comctl32:taskdialog returned an error (3221226356) despite having no failures
comctl32:taskdialog has no test summary line (early exit of the main process?)

=== w864 (64 bit taskdialog) ===
comctl32:taskdialog returned an error (3221226356) despite having no failures
comctl32:taskdialog has no test summary line (early exit of the main process?)

=== w1064 (64 bit taskdialog) ===
comctl32:taskdialog returned an error (3221226356) despite having no failures
comctl32:taskdialog has no test summary line (early exit of the main process?)

[v3 09/12] comctl32: TaskDialog - Changed tests to allow sending messages

[Fabian Maurer]

> === w1064 (64 bit taskdialog) ===
> comctl32:taskdialog returned an error (3221226356) despite having no
> failures comctl32:taskdialog has no test summary line (early exit of the
> main process?)
> Yes, there seems to be a problem with 64bit taskdialog. I'll investigate why 
> it crashes.

Regards,
Fabian Maurer