[PATCH 3/5] ntoskrnl.exe/tests: Add some HidD_GetFeature tests.

Rémi Bernon rbernon at codeweavers.com
Thu Jul 1 03:39:28 CDT 2021


On 7/1/21 10:35 AM, Marvin wrote:
> === debiant2 (32 bit report) ===
> 
> ntoskrnl.exe:
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> 
> Report validation errors:
> ntoskrnl.exe:ntoskrnl returned success despite having failures
> 
> === debiant2 (32 bit Arabic:Morocco report) ===
> 
> ntoskrnl.exe:
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctlsexpected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> 
> Report validation errors:
> ntoskrnl.exe:ntoskrnl returned success despite having failures
> 
> === debiant2 (32 bit German report) ===
> 
> ntoskrnl.exe:
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> 
> Report validation errors:
> ntoskrnl.exe:ntoskrnl returned success despite having failures
> 
> === debiant2 (32 bit French report) ===
> 
> ntoskrnl.exe:
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> 
> Report validation errors:
> ntoskrnl.exe:ntoskrnl returned success despite having failures
> 
> === debiant2 (32 bit Hebrew:Israel report) ===
> 
> ntoskrnl.exe:
> driver_hid.c:307: Test succeeded inside todo block: got packet buffer len 22, expected 23 or more
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> 
> Report validation errors:
> ntoskrnl.exe:ntoskrnl returned success despite having failures
> 
> === debiant2 (32 bit Hindi:India report) ===
> 
> ntoskrnl.exe:
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctlsexpected IRP_MN_START_DEVICE before any ioctls
> 
> Report validation errors:
> ntoskrnl.exe:ntoskrnl returned success despite having failures
> 
> === debiant2 (32 bit Japanese:Japan report) ===
> 
> ntoskrnl.exe:
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> 
> Report validation errors:
> ntoskrnl.exe:ntoskrnl returned success despite having failures
> 
> === debiant2 (32 bit Chinese:China report) ===
> 
> ntoskrnl.exe:
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> 
> Report validation errors:
> ntoskrnl.exe:ntoskrnl returned success despite having failures
> 
> === debiant2 (64 bit WoW report) ===
> 
> ntoskrnl.exe:
> driver_hid.c:307: Test succeeded inside todo block: expected IRP_MN_START_DEVICE before any ioctls
> 
> Report validation errors:
> ntoskrnl.exe:ntoskrnl returned success despite having failures
> 

This test isn't even marked todo_wine?! And of course I can't reproduce 
the failure locally either.
-- 
Rémi Bernon <rbernon at codeweavers.com>



More information about the wine-devel mailing list