TestBot job 87490 results: [PATCH 3/5] include: Add missing items_size parameter to GetMany.

[Rémi Bernon]

On 3/23/21 10:13 AM, Marvin wrote:
> VM                   Status   Failures Command
> build                success
> w2008s64             success  0        windows.gaming.input_test.exe input
> w7u_2qxl             success  0        windows.gaming.input_test.exe input
> w7u_adm              success  0        windows.gaming.input_test.exe input
> w7u_el               success  0        windows.gaming.input_test.exe input
> w8                   success  0        windows.gaming.input_test.exe input
> w8adm                success  0        windows.gaming.input_test.exe input
> w864                 success  0        windows.gaming.input_test.exe input
> w1064v1507           failed   1        windows.gaming.input_test.exe input
> w1064v1809           failed   2        windows.gaming.input_test.exe input
> w1064                failed   2        windows.gaming.input_test.exe input
> w10pro64             failed   2        windows.gaming.input_test.exe input
> wvistau64            success  0        windows.gaming.input_test64.exe input
> w2008s64             success  0        windows.gaming.input_test64.exe input
> w864                 success  0        windows.gaming.input_test64.exe input
> w1064v1507           failed   1        windows.gaming.input_test64.exe input
> w1064v1809           failed   2        windows.gaming.input_test64.exe input
> w1064                failed   2        windows.gaming.input_test64.exe input
> w1064_2qxl           failed   2        windows.gaming.input_test64.exe input
> w10pro64             failed   2        windows.gaming.input_test64.exe input
> w10pro64_ar          failed   2        windows.gaming.input_test64.exe input
> w10pro64_he          failed   2        windows.gaming.input_test64.exe input
> w10pro64_ja          failed   2        windows.gaming.input_test64.exe input
> w10pro64_zh_CN       failed   2        windows.gaming.input_test64.exe input
> w2008s64             success  0        windows.media.speech_test.exe speech
> w7u_2qxl             success  0        windows.media.speech_test.exe speech
> w7u_adm              success  0        windows.media.speech_test.exe speech
> w7u_el               success  0        windows.media.speech_test.exe speech
> w8                   success  0        windows.media.speech_test.exe speech
> w8adm                success  0        windows.media.speech_test.exe speech
> w864                 success  0        windows.media.speech_test.exe speech
> w1064v1507           success  0        windows.media.speech_test.exe speech
> w1064v1809           success  0        windows.media.speech_test.exe speech
> w1064                success  0        windows.media.speech_test.exe speech
> w10pro64             success  0        windows.media.speech_test.exe speech
> wvistau64            success  0        windows.media.speech_test64.exe speech
> w2008s64             success  0        windows.media.speech_test64.exe speech
> w864                 success  0        windows.media.speech_test64.exe speech
> w1064v1507           success  0        windows.media.speech_test64.exe speech
> w1064v1809           success  0        windows.media.speech_test64.exe speech
> w1064                success  0        windows.media.speech_test64.exe speech
> w1064_2qxl           success  0        windows.media.speech_test64.exe speech
> w10pro64             success  0        windows.media.speech_test64.exe speech
> w10pro64_ar          success  0        windows.media.speech_test64.exe speech
> w10pro64_he          success  0        windows.media.speech_test64.exe speech
> w10pro64_ja          success  0        windows.media.speech_test64.exe speech
> w10pro64_zh_CN       success  0        windows.media.speech_test64.exe speech
> debiant2             success  0
> debiant2             success  0
> 
> You can also see the results at:
> https://testbot.winehq.org/JobDetails.pl?Key=87490
> 
> 
> === w1064v1507 (32 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> 
> === w1064v1809 (32 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w1064 (32 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w10pro64 (32 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w1064v1507 (64 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> 
> === w1064v1809 (64 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w1064 (64 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w1064_2qxl (64 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w10pro64 (64 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w10pro64_ar (64 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w10pro64_he (64 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w10pro64_ja (64 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 
> === w10pro64_zh_CN (64 bit report) ===
> 
> windows.gaming.input:
> input.c:179: Test failed: IVectorView_Gamepad_GetMany failed, hr 0x8000000b
> input.c:351: Test failed: IVectorView_RawGameController_GetMany failed, hr 0x8000000b
> 

I'll fix these, a bit weird that we get E_BOUNDS when vector is empty, 
but not when it isn't (as in windows.media.speech voices tests), even 
though the requested range is always out of bounds?
-- 
Rémi Bernon <rbernon at codeweavers.com>