[PATCH 0/1] MR7197: propsys: Remove FIXME() from PropVariantChangeType().

[Nikolay Sivov (＠nsivov)]

We have a fixme for types that are not yet supported.

Signed-off-by: Nikolay Sivov

[PATCH 1/1] propsys: Remove FIXME() from PropVariantChangeType().

[Nikolay Sivov]

From: Nikolay Sivov

We have a fixme for types that are not yet supported.

Signed-off-by: Nikolay Sivov 
---
 dlls/propsys/propvar.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/dlls/propsys/propvar.c b/dlls/propsys/propvar.c
index c5d86c0027c..5d776ed8dcf 100644
--- a/dlls/propsys/propvar.c
+++ b/dlls/propsys/propvar.c
@@ -604,8 +604,7 @@ HRESULT WINAPI PropVariantChangeType(PROPVARIANT *ppropvarDest, REFPROPVARIANT p
 {
     HRESULT hr;

-    FIXME("(%p, %p, %d, %d, %d): semi-stub!\n", ppropvarDest, propvarSrc,
-          propvarSrc->vt, flags, vt);
+    TRACE("(%p, %p, %d, %d, %d)\n", ppropvarDest, propvarSrc, propvarSrc->vt, flags, vt);

if (vt == propvarSrc->vt)
         return PropVariantCopy(ppropvarDest, propvarSrc);

[PATCH 1/1] propsys: Remove FIXME() from PropVariantChangeType().

[Marvin]

Hi,

It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.

The tests also ran into some preexisting test failures. If you know how
to fix them that would be helpful. See the TestBot job for the details:

The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=151062

Your paranoid android.

=== debian11b (64 bit WoW report) ===

user32:
input.c:4306: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 0000000000540100, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032
msg.c:6995: Test failed: SetFocus(hwnd) on a button: 3: the winevent_hook 0x8005 was expected, but got hook 0x0005 instead
msg.c:6995: Test failed: SetFocus(hwnd) on a button: 3: the winevent_hook 0x8005 was expected, but got winevent_hook 0x0003 instead
msg.c:6995: Test failed: SetFocus(hwnd) on a button: 3: the winevent_hook 0x8005 was expected, but got msg 0x030f instead
msg.c:6995: Test failed: SetFocus(hwnd) on a button: 3: the winevent_hook 0x8005 was expected, but got msg 0x001c instead
msg.c:6995: Test failed: SetFocus(hwnd) on a button: 3: the winevent_hook 0x8005 was expected, but got msg 0x0086 instead
msg.c:6995: Test failed: SetFocus(hwnd) on a button: 3: the winevent_hook 0x8005 was expected, but got msg 0x0006 instead
msg.c:6995: Test failed: SetFocus(hwnd) on a button: 3: the winevent_hook 0x8005 was expected, but got hook 0x0009 instead