November 2011 - Wine-devel - list.winehq.org

Re: [1/2] kernel32: Add a test for protections accepted by CreateFileMapping, make it pass under Wine.
by Alexandre Julliard 28 Nov '11

28 Nov '11

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > @@ -350,9 +350,6 @@ HANDLE WINAPI CreateFileMappingW( HANDLE hFile, LPSECURITY_ATTRIBUTES sa, > > switch(protect) > { > - case 0: > - protect = PAGE_READONLY; /* Win9x compatibility */ > - /* fall through */ Did you try your test on Win9x? -- Alexandre Julliard julliard(a)winehq.org

3 6

Re: [3/5] cmd/tests: Tweak subsection headers so they are treated as resynchronization points.
by Marvin 28 Nov '11

28 Nov '11

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 http://testbot.winehq.org/JobDetails.pl?Key=15676 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/5] cmd/tests: Standardize the batch file section headers.
by Marvin 28 Nov '11

28 Nov '11

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 http://testbot.winehq.org/JobDetails.pl?Key=15675 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/5] cmd/tests: Standardize the batch file section headers.
by Marvin 28 Nov '11

28 Nov '11

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 http://testbot.winehq.org/JobDetails.pl?Key=15675 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/5] cmd/tests: Standardize the batch file section headers.
by Marvin 28 Nov '11

28 Nov '11

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 http://testbot.winehq.org/JobDetails.pl?Key=15675 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/5] cmd/tests: Standardize the batch file section headers.
by Marvin 28 Nov '11

28 Nov '11

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 http://testbot.winehq.org/JobDetails.pl?Key=15675 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: kernel32/tests: Test deleting a timer right after creating it.
by Marvin 28 Nov '11

28 Nov '11

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 http://testbot.winehq.org/JobDetails.pl?Key=15671 Your paranoid android. === W2KPROSP4 (32 bit sync) === sync.c:685: Test failed: DeleteTimerQueueTimer ret=1 le=997 === WXPPROSP3 (32 bit sync) === sync.c:685: Test failed: DeleteTimerQueueTimer ret=1 le=997 === W2K3R2SESP2 (32 bit sync) === sync.c:685: Test failed: DeleteTimerQueueTimer ret=1 le=997 === WVISTAADM (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === W2K8SE (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === W7PRO (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === W7PROX64 (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === TEST64_W7SP1 (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === W7PROX64 (64 bit sync) === sync.c:741: Test failed: Timer callback 0 === TEST64_W7SP1 (64 bit sync) === sync.c:741: Test failed: Timer callback 0

1 0

Re: [PATCH] dxgi: 0 / 0 means 0 for a DXGI_RATIONAL
by Marvin 28 Nov '11

28 Nov '11

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 http://testbot.winehq.org/JobDetails.pl?Key=15670 Your paranoid android. === WVISTAADM (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === W2K8SE (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === W7PRO (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === W7PROX64 (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === TEST64_W7SP1 (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === W7PROX64 (64 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. Timeout === TEST64_W7SP1 (64 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. Timeout

1 0

Re: [PATCH 1/5] user32/tests: Initial tests for RawInput functions.
by Marvin 28 Nov '11

28 Nov '11

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 http://testbot.winehq.org/JobDetails.pl?Key=15663 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W2K8SE (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PRO (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (64 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (64 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87

2 1

Re: [PATCH 5/5] user32: Implement GetRawInputDeviceInfoW completely on user side.
by Marvin 28 Nov '11

28 Nov '11

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 http://testbot.winehq.org/JobDetails.pl?Key=15666 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W2K8SE (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PRO (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (64 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (64 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87

1 0