[PATCH 4/7] msi: Return ERROR_INVALID_HANDLE when MsiDatabaseExport() is called from a custom action.

Marvin testbot at winehq.org
Tue Mar 26 04:28:16 CDT 2019


Hi,

While running your changed tests, 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=49926

Your paranoid android.


=== w7u (32 bit report) ===

msi:
action: Timeout

=== w1064 (64 bit report) ===

msi:
action.c:6274: Test failed: Expected ERROR_SUCCESS, got 1618
action.c:6284: Test failed: Expected ERROR_SUCCESS, got 2
action.c:6285: Test failed: Key doesn't exist or wrong type
action.c:6290: Test failed: Expected ERROR_SUCCESS, got 2
action.c:6291: Test failed: Key doesn't exist or wrong type
action.c:6295: Test failed: Expected ERROR_SUCCESS, got 2
action.c:6296: Test failed: Key doesn't exist or wrong type
action.c:6301: Test failed: Expected ERROR_SUCCESS, got 2
action.c:6302: Test failed: Key doesn't exist or wrong type
action.c:6311: Test failed: Expected ERROR_SUCCESS, got 1605

=== wxppro (32 bit report) ===

msi:
custom.c:1134: Test failed: got 1620

Report errors:
msi:install contains a misplaced failure message for custom

=== w7u (32 bit report) ===

msi:
install: Timeout

=== w7u (task log) ===

Task errors:
The task timed out

=== w2008s64 (64 bit report) ===

msi:
install: Timeout

=== w7u (32 bit report) ===

msi:
msi: Timeout



More information about the wine-devel mailing list