October 2013 - Wine-Devel - list.winehq.org

Re: [PATCH 3/5] ddraw/tests: Make caps checking in test_rt_caps() less strict.
by Marvin Oct. 25, 2013

Oct. 25, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=3032 Your paranoid android. === w864 (32 bit ddraw7) === The test timed out === w864 (32 bit ddraw4) === The test timed out

1 0

Re: [PATCH 1/5] ddraw/tests: Accept nvidia return values in test_rt_caps.
by Marvin Oct. 25, 2013

Oct. 25, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=3030 Your paranoid android. === w864 (32 bit ddraw2) === ddraw2: unhandled exception c0000005 at 00420E61 === w864 (32 bit ddraw7) === No test summary line found Failure running script in VM: network read timed out

1 0

Re: winspool.drv/tests: Fix tests compilation with __WINESRC__ defined (try 2)
by Marvin Oct. 24, 2013

Oct. 24, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=3019 Your paranoid android. === w864 (32 bit info) === info: unhandled exception c0000005 at 0040B246 === w864 (64 bit info) === info.c:2932: Test failed: got NULL DEVMODEA info: unhandled exception c0000005 at 00000000004099CD

1 0

Re: [PATCH 6/6] ole32: If an object exposes IExternalConnection then don't take down the stub manager if we have remaining w
by Marvin Oct. 24, 2013

Oct. 24, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=3010 Your paranoid android. === w864 (32 bit marshal) === marshal.c:3318: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3319: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3335: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3336: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3373: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3374: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3391: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3392: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3355: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3356: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3318: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3319: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3335: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3336: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3373: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3374: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3391: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3392: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3355: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3356: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3318: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3319: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3335: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3336: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3373: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3374: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3391: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3392: Test failed: info->dwServerPid was 0x874 instead of 0x904 marshal.c:3355: Test failed: info->cbSize was -737179689 instead of 48 marshal.c:3356: Test failed: info->dwServerPid was 0x874 instead of 0x904 === w864 (64 bit marshal) === marshal.c:3318: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3319: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3335: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3336: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3373: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3374: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3391: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3392: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3355: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3356: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3318: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3319: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3335: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3336: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3373: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3374: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3391: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3392: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3355: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3356: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3318: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3319: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3335: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3336: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3373: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3374: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3391: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3392: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48 marshal.c:3355: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3356: Test failed: info->dwServerPid was 0xaa4 instead of 0xa48

1 0

Re: [PATCH 5/6] ole32: Call IExternalConnection_ReleaseConnection with the correct final parameter.
by Marvin Oct. 24, 2013

Oct. 24, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=3009 Your paranoid android. === w864 (32 bit marshal) === marshal.c:3321: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3322: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3338: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3339: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3376: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3377: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3394: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3395: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3358: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3359: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3321: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3322: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3338: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3339: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3376: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3377: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3394: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3395: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3358: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3359: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3321: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3322: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3338: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3339: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3376: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3377: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3394: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3395: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 marshal.c:3358: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3359: Test failed: info->dwServerPid was 0xb60 instead of 0xa48 === w864 (64 bit marshal) === marshal.c:3321: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3322: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3338: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3339: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3376: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3377: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3394: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3395: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3358: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3359: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3321: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3322: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3338: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3339: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3376: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3377: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3394: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3395: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3358: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3359: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3321: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3322: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3338: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3339: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3376: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3377: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3394: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3395: Test failed: info->dwServerPid was 0x86c instead of 0xbb0 marshal.c:3358: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3359: Test failed: info->dwServerPid was 0x86c instead of 0xbb0

1 0

Re: [PATCH 4/6] ole32: When releasing marshal data of a normal ref ignore any remaining weak refs.
by Marvin Oct. 24, 2013

Oct. 24, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=3008 Your paranoid android. === w864 (32 bit marshal) === marshal.c:3326: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3327: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3343: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3344: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3381: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3382: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3399: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3400: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3363: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3364: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3326: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3327: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3343: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3344: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3381: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3382: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3399: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3400: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3363: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3364: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3326: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3327: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3343: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3344: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3381: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3382: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3399: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3400: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 marshal.c:3363: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3364: Test failed: info->dwServerPid was 0x5bc instead of 0xac8 === w864 (64 bit marshal) === marshal.c:3326: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3327: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3343: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3344: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3381: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3382: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3399: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3400: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3363: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3364: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3326: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3327: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3343: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3344: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3381: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3382: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3399: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3400: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3363: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3364: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3326: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3327: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3343: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3344: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3381: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3382: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3399: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3400: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74 marshal.c:3363: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3364: Test failed: info->dwServerPid was 0x8e4 instead of 0xb74

1 0

Re: [PATCH 3/6] ole32/tests: Add some tests for CoReleaseMarshalData with a combination of normal and weak marshals.
by Marvin Oct. 24, 2013

Oct. 24, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=3007 Your paranoid android. === w864 (32 bit marshal) === marshal.c:3326: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3327: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3343: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3344: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3381: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3382: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3399: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3400: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3363: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3364: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3326: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3327: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3343: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3344: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3381: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3382: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3399: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3400: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3363: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3364: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3326: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3327: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3343: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3344: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3381: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3382: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3399: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3400: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 marshal.c:3363: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3364: Test failed: info->dwServerPid was 0xaa4 instead of 0xb54 === w864 (64 bit marshal) === marshal.c:3326: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3327: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3343: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3344: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3381: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3382: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3399: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3400: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3363: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3364: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3326: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3327: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3343: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3344: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3381: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3382: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3399: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3400: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3363: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3364: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3326: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3327: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3343: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3344: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3381: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3382: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3399: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3400: Test failed: info->dwServerPid was 0x118 instead of 0xba4 marshal.c:3363: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3364: Test failed: info->dwServerPid was 0x118 instead of 0xba4

1 0

Re: [PATCH 2/6] ole32/tests: Make the two reference marshalling thread more generic.
by Marvin Oct. 24, 2013

Oct. 24, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=3006 Your paranoid android. === w864 (32 bit marshal) === marshal.c:3230: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3231: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3247: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3248: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3285: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3286: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3303: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3304: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3267: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3268: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3230: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3231: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3247: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3248: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3285: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3286: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3303: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3304: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3267: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3268: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3230: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3231: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3247: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3248: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3285: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3286: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3303: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3304: Test failed: info->dwServerPid was 0x370 instead of 0xa48 marshal.c:3267: Test failed: info->cbSize was 1527466381 instead of 48 marshal.c:3268: Test failed: info->dwServerPid was 0x370 instead of 0xa48 === w864 (64 bit marshal) === marshal.c:3230: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3231: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3247: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3248: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3285: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3286: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3303: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3304: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3267: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3268: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3230: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3231: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3247: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3248: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3285: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3286: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3303: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3304: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3267: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3268: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3230: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3231: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3247: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3248: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3285: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3286: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3303: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3304: Test failed: info->dwServerPid was 0x738 instead of 0xbb8 marshal.c:3267: Test failed: info->cbSize was -1047396882 instead of 56 marshal.c:3268: Test failed: info->dwServerPid was 0x738 instead of 0xbb8

1 0

Re: [PATCH 1/6] ole32/tests: Extend the lifecycle tests to objects which expose IExternalConnection.
by Marvin Oct. 24, 2013

Oct. 24, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=3005 Your paranoid android. === w864 (32 bit marshal) === marshal.c:3226: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3227: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3243: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3244: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3281: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3282: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3299: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3300: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3263: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3264: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3226: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3227: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3243: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3244: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3281: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3282: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3299: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3300: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3263: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3264: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3226: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3227: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3243: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3244: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3281: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3282: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3299: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3300: Test failed: info->dwServerPid was 0x870 instead of 0xbac marshal.c:3263: Test failed: info->cbSize was -1846173327 instead of 48 marshal.c:3264: Test failed: info->dwServerPid was 0x870 instead of 0xbac === w864 (64 bit marshal) === marshal.c:3226: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3227: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3243: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3244: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3281: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3282: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3299: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3300: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3263: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3264: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3226: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3227: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3243: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3244: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3281: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3282: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3299: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3300: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3263: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3264: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3226: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3227: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3243: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3244: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3281: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3282: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3299: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3300: Test failed: info->dwServerPid was 0x18c instead of 0xa48 marshal.c:3263: Test failed: info->cbSize was -588349091 instead of 56 marshal.c:3264: Test failed: info->dwServerPid was 0x18c instead of 0xa48

1 0

Re: server: Add support for pending write flag to the serial device. Take 2.
by Alexandre Julliard Oct. 24, 2013

Oct. 24, 2013

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > This patch makes WaitCommEvent(EV_TXEMPTY) work when a serial device > reports that the out queue is empty even after a successful write() > which is the case for real COM ports and as well as for serial-USB > adapters. > > Take 2 removes special handling of FlushFileBuffers for a serial sevice, > the tests show that it really should not reset the pending write state. > > I'd like to see some feedback for this patch. It doesn't work here: ../../../tools/runtest -q -P wine -T ../../.. -M kernel32.dll -p kernel32_test.exe.so comm.c && touch comm.ok comm.c:860: Test failed: WaitCommEvent failed with a timeout comm.c:881: Test failed: WaitCommEvent error 997 comm.c:882: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:887: Test failed: WaitCommEvent used 1003 ms for waiting comm.c:2226: Tests skipped: interactive tests (set WINETEST_INTERACTIVE=1) make: *** [comm.ok] Error 4 -- Alexandre Julliard julliard(a)winehq.org

3 10

Re: [5/7] oleaut32/tests: Fix typelib tests compilation with __WINESRC__ defined
by Dmitry Timoshkov Oct. 24, 2013

Oct. 24, 2013

André Hentschel <nerv(a)dawncrow.de> wrote: > - ok(lstrcmp(value, buf) == 0, #expr " expected \"%s\" got \"%s\"\n", value, buf); \ > + ok(lstrcmpA(value, buf) == 0, #expr " expected \"%s\" got \"%s\"\n", value, buf); \ Using simple strcmp() should be preferrable, leaving lstr* versions only for cases when an exception handler is really needed. P.S. Fixing compilation with __WINESRC__ defined gives an opportunity for reviewing the code, this should not be a simple search and replace job. -- Dmitry.

1 0

Re: winspool.drv/tests: Fix tests compilation with __WINESRC__ defined
by Dmitry Timoshkov Oct. 24, 2013

Oct. 24, 2013

André Hentschel <nerv(a)dawncrow.de> wrote: > @@ -3018,28 +3018,28 @@ START_TEST(info) > test_ConfigurePort(); > test_DeleteMonitor(); > test_DeletePort(); > - test_DeviceCapabilities(); > - test_DocumentProperties(); > + test_DeviceCapabilitiesA(); > + test_DocumentPropertiesA(); > test_EnumForms(NULL); > if (default_printer) test_EnumForms(default_printer); > test_EnumMonitors(); > - test_EnumPorts(); > + test_EnumPortsA(); > test_EnumPrinterDrivers(); > test_EnumPrinters(); > test_EnumPrintProcessors(); > test_GetDefaultPrinter(); > test_GetPrinterDriverDirectory(); > test_GetPrintProcessorDirectory(); > - test_OpenPrinter(); > - test_GetPrinter(); > + test_OpenPrinterA(); > + test_GetPrinterA(); > test_GetPrinterData(); > test_GetPrinterDataEx(); > - test_GetPrinterDriver(); > + test_GetPrinterDriverA(); > test_SetDefaultPrinter(); > test_XcvDataW_MonitorUI(); > test_XcvDataW_PortIsValid(); > test_IsValidDevmodeW(); > - test_OpenPrinter_defaults(); > + test_OpenPRINTER_DEFAULTSA(); Please leave the test names intact, that assumes that adding tests for W version of an API doesn't need a separate body. -- Dmitry.

1 0

Re: winspool.drv/tests: Fix tests compilation with __WINESRC__ defined
by Marvin Oct. 24, 2013

Oct. 24, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2988 Your paranoid android. === w864 (32 bit info) === info.c:2925: Test failed: got 0 info.c:2931: Test failed: got 0 info: unhandled exception c0000005 at 0040B246 === w864 (64 bit info) === info.c:2934: Test failed: got NULL DEVMODEA info: unhandled exception c0000005 at 00000000004099CD

1 0

Re: winemac: Add registry settings to make Option keys send Alt rather than accessing additional characters from the keyboard layout.
by Phil Krylov Oct. 24, 2013

Oct. 24, 2013

Thanks! Do you consider adding an option to stop interpreting Command as Alt? On Thu, Oct 10, 2013 at 1:30 AM, Ken Thomases <ken(a)codeweavers.com> wrote: > --- > dlls/winemac.drv/cocoa_window.m | 22 ++++++++++++++++++++-- > dlls/winemac.drv/macdrv_cocoa.h | 2 ++ > dlls/winemac.drv/macdrv_main.c | 7 +++++++ > 3 files changed, 29 insertions(+), 2 deletions(-) > > > > -- С уважением, Филипп Крылов.

2 5

Re: [PATCH 2/6] user32: Implement OpenInputDesktop.
by Alexandre Julliard Oct. 23, 2013

Oct. 23, 2013

Qian Hong <qhong(a)codeweavers.com> writes: > Hello, > > This patch superseded patch 99498. > Thanks Vincent Povirk for the previous comment, now I try to implement > OpenInputDesktop in user32 and server. I don't think that makes sense, under Wine every desktop is potentially an input desktop, there's no way to decide which one is the "real" one. -- Alexandre Julliard julliard(a)winehq.org

2 3

Re: [PATCH 2/2] user32: Implement OpenInputDesktop.
by Marvin Oct. 23, 2013

Oct. 23, 2013

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

1 0

Re: ole32: Support activation context in CLSIDFromProgID()
by Alexandre Julliard Oct. 23, 2013

Oct. 23, 2013

Nikolay Sivov <nsivov(a)codeweavers.com> writes: > Support activation context in CLSIDFromProgID() It breaks the tests: ../../../tools/runtest -q -P wine -T ../../.. -M msi.dll -p msi_test.exe.so msi.c && touch msi.ok msi.c:1974: Test failed: expected 0xdeadbeef, got 14007 msi.c:1981: Test failed: expected 0xdeadbeef, got 14007 msi.c:1988: Test failed: expected 0xdeadbeef, got 14007 msi.c:2003: Test failed: expected 0xdeadbeef, got 14007 msi.c:2506: Test failed: expected 0xdeadbeef, got 14007 msi.c:2515: Test failed: expected 0xdeadbeef, got 14007 make: *** [msi.ok] Error 6 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 3/3] ddraw/tests: Test DDSCAPS2_D3DTEXTUREMANAGE.
by Marvin Oct. 23, 2013

Oct. 23, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2973 Your paranoid android. === w864 (32 bit ddraw7) === No test summary line found Failure running script in VM: network read timed out === w864 (64 bit ddraw7) === ddraw7.c:3695: Test failed: Got unexpected, hr 0x80004002, case 4. ddraw7.c:3695: Test failed: Got unexpected, hr 0x80004002, case 5. ddraw7.c:3695: Test failed: Got unexpected, hr 0x80004002, case 6. ddraw7.c:3695: Test failed: Got unexpected, hr 0x80004002, case 7. === w864 (32 bit ddraw4) === The test timed out

1 0

Re: [PATCH 1/3] ddraw/tests: Add surface lockability tests.
by Marvin Oct. 23, 2013

Oct. 23, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2972 Your paranoid android. === w864 (32 bit ddraw2) === The test timed out === w864 (32 bit ddraw1) === ddraw1: unhandled exception c0000005 at 0041212F === w864 (32 bit ddraw7) === Timeout Failure running script in VM: network read timed out === w864 (64 bit ddraw7) === ddraw7.c:3683: Test failed: Got unexpected, hr 0x80004002, case 2. ddraw7.c:3683: Test failed: Got unexpected, hr 0x80004002, case 3. ddraw7.c:3683: Test failed: Got unexpected, hr 0x80004002, case 4. === w864 (32 bit ddraw4) === Failure running script in VM: network read timed out

2 1

Re: [23/23] user32/tests: Enable user32 tests compilation with __WINESRC__ defined.
by Marvin Oct. 23, 2013

Oct. 23, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2971 Your paranoid android. === wxppro (32 bit) === No test summary line found === wvista (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7pro64 (32 bit) === No test summary line found === w864 (32 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found === w7pro64 (64 bit) === No test summary line found === w864 (64 bit) === No test summary line found

1 0

Re: [02/02] d3d8: update locked_rect only if wined3d_surface_map succeeds
by Henri Verbeet Oct. 23, 2013

Oct. 23, 2013

On 21 October 2013 10:47, Lasse Rasinen <lrasinen(a)iki.fi> wrote: > diff --git a/dlls/d3d8/tests/device.c b/dlls/d3d8/tests/device.c > index 7932a7f..52cf27a 100644 > --- a/dlls/d3d8/tests/device.c > +++ b/dlls/d3d8/tests/device.c > @@ -4022,8 +4022,12 @@ static void test_lockrect_invalid(void) > > hr = IDirect3DSurface8_LockRect(surface, &locked_rect, NULL, 0); > ok(SUCCEEDED(hr), "Failed to lock surface with rect NULL, hr %#x.\n", hr); > + locked_rect.pBits = 0xdeadbeef; > + locked_rect.Pitch = 1; > hr = IDirect3DSurface8_LockRect(surface, &locked_rect, NULL, 0); > ok(hr == D3DERR_INVALIDCALL, "Got unexpected hr %#x.\n", hr); > + ok(locked_rect.pBits == 0xdeadbeef, "pBits changed on double lock.\n"); > + ok(locked_rect.Pitch == 1, "Pitch changed on double lock.\n"); > hr = IDirect3DSurface8_UnlockRect(surface); > ok(SUCCEEDED(hr), "Failed to unlock surface, hr %#x.\n", hr); > This test fails for me on Windows 7: device.c:4029: Test failed: pBits changed on double lock. device.c:4030: Test failed: Pitch changed on double lock. As an aside, if you had written the messages as "Got unexpected pBits %p.\n" and "Got unexpected Pitch %d.\n", you would have gotten the following output instead: device.c:4029: Test failed: Got unexpected pBits 00000000. device.c:4030: Test failed: Got unexpected Pitch 0.

3 6

Re: [20/23] user32/tests: Fix window tests compilation with __WINESRC__ defined.
by Marvin Oct. 23, 2013

Oct. 23, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2968 Your paranoid android. === wxppro (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 000700E2 fg 00030040 in hook HCBT_ACTIVATE win.c:2951: Test failed: GetActiveWindow() = 00000000 win.c:2951: Test failed: GetFocus() = 00000000 win.c:2974: Test failed: GetActiveWindow() = 00000000 win.c:2974: Test failed: GetFocus() = 00000000 win.c:3035: Test failed: GetActiveWindow() = 00000000 win.c:3035: Test failed: GetFocus() = 00000000 === wvista (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 000701F6 fg 00010046 in hook HCBT_ACTIVATE win.c:2951: Test failed: GetActiveWindow() = 00000000 win.c:2951: Test failed: GetFocus() = 00000000 win.c:2974: Test failed: GetActiveWindow() = 00000000 win.c:2974: Test failed: GetFocus() = 00000000 win.c:3035: Test failed: GetActiveWindow() = 00000000 win.c:3035: Test failed: GetFocus() = 00000000 === w2008s64 (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 000500F4 fg 0001004E in hook HCBT_ACTIVATE win.c:2951: Test failed: GetActiveWindow() = 00000000 win.c:2951: Test failed: GetFocus() = 00000000 win.c:2974: Test failed: GetActiveWindow() = 00000000 win.c:2974: Test failed: GetFocus() = 00000000 win.c:3035: Test failed: GetActiveWindow() = 00000000 win.c:3035: Test failed: GetFocus() = 00000000 === w7pro64 (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 00090138 fg 00010066 in hook HCBT_ACTIVATE win.c:2951: Test failed: GetActiveWindow() = 00000000 win.c:2951: Test failed: GetFocus() = 00000000 win.c:2974: Test failed: GetActiveWindow() = 00000000 win.c:2974: Test failed: GetFocus() = 00000000 win.c:3035: Test failed: GetActiveWindow() = 00000000 win.c:3035: Test failed: GetFocus() = 00000000 === w864 (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 000601BA fg 00010084 in hook HCBT_ACTIVATE win.c:2951: Test failed: GetActiveWindow() = 00000000 win.c:2951: Test failed: GetFocus() = 00000000 win.c:2974: Test failed: GetActiveWindow() = 00000000 win.c:2974: Test failed: GetFocus() = 00000000 win.c:3035: Test failed: GetActiveWindow() = 00000000 win.c:3035: Test failed: GetFocus() = 00000000 === w2008s64 (64 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 00000000000500F4 fg 000000000001004E in hook HCBT_ACTIVATE win.c:2951: Test failed: GetActiveWindow() = 0000000000000000 win.c:2951: Test failed: GetFocus() = 0000000000000000 win.c:2974: Test failed: GetActiveWindow() = 0000000000000000 win.c:2974: Test failed: GetFocus() = 0000000000000000 win.c:3035: Test failed: GetActiveWindow() = 0000000000000000 win.c:3035: Test failed: GetFocus() = 0000000000000000 === w7pro64 (64 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 0000000000090138 fg 0000000000010066 in hook HCBT_ACTIVATE win.c:2951: Test failed: GetActiveWindow() = 0000000000000000 win.c:2951: Test failed: GetFocus() = 0000000000000000 win.c:2974: Test failed: GetActiveWindow() = 0000000000000000 win.c:2974: Test failed: GetFocus() = 0000000000000000 win.c:3035: Test failed: GetActiveWindow() = 0000000000000000 win.c:3035: Test failed: GetFocus() = 0000000000000000

1 0

Re: [18/23] user32/tests: Fix system parameters tests compilation with __WINESRC__ defined.
by Marvin Oct. 23, 2013

Oct. 23, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2966 Your paranoid android. === w864 (32 bit sysparams) === sysparams.c:2792: Test failed: GetSystemMetrics(SM_CXMAXTRACK): expected 1044 or 1036 actual 1040 sysparams.c:2794: Test failed: GetSystemMetrics(SM_CYMAXTRACK): expected 788 or 780 actual 784 sysparams.c:2490: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2503: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1 === w864 (64 bit sysparams) === sysparams.c:2792: Test failed: GetSystemMetrics(SM_CXMAXTRACK): expected 1044 or 1036 actual 1040 sysparams.c:2794: Test failed: GetSystemMetrics(SM_CYMAXTRACK): expected 788 or 780 actual 784 Timeout

1 0

Re: [10/23] user32/tests: Fix input tests compilation with __WINESRC__ defined.
by Saulius Krasuckas Oct. 23, 2013

Oct. 23, 2013

* On Wed, 23 Oct 2013, Dmitry Timoshkov wrote: > --- a/dlls/user32/tests/input.c > +++ b/dlls/user32/tests/input.c > @@ -929,7 +929,7 @@ static void test_Input_blackbox(void) > * key state set by SendInput(). */ > empty_message_queue(); > > - prevWndProc = SetWindowLongPtr(window, GWLP_WNDPROC, (LONG_PTR) WndProc2); > + prevWndProc = SetWindowLongPtrA(window, GWLP_WNDPROC, (LONG_PTR) WndProc2); > ok(prevWndProc != 0 || (prevWndProc == 0 && GetLastError() == 0), > "error: %d\n", (int) GetLastError()); > * On Fri, 8 Jun 2007, Saulius Krasuckas wrote: > --- a/dlls/user32/tests/input.c > +++ b/dlls/user32/tests/input.c > @@ -496,7 +496,7 @@ static void test_Input_blackbox(void) > * key state set by SendInput(). */ > empty_message_queue(); > > - prevWndProc = SetWindowLongPtr(window, GWLP_WNDPROC, (LONG_PTR) WndProc2); > + prevWndProc = SetWindowLongPtrA(window, GWLP_WNDPROC, (LONG_PTR) WndProc2); > ok(prevWndProc != 0 || (prevWndProc == 0 && GetLastError() == 0), > "error: %d\n", (int) GetLastError()); > It's nice to see the change is being offered by it's previous opponent six years later. Since Dmitry was strongly against it, questions go to him: * On Sat, 9 Jun 2007, Dmitry Timoshkov wrote: > "Saulius Krasuckas" <saulius2(a)ar.fi.lt> wrote: > > > Hello. I see some tests call [GS]etWindowLongPtr(..., GWLP_WNDPROC, > > ...). I think this is somewhat confusing. API offers both A- an W- > > versions of this function, while at my first glance I cannot firmly > > decide, what used name does refer to. > > > > Shouldn't occurences be renamed to ...WindowLongPtrA() here (or even > > all occurrences {by not requiring second parameter == GWLP_WNDPROC}) ? > > > > Same question stands for [GS]etWindowLong(). > > The code is correct as it is now, there is no need to change anything. Dmitry, what has changed since? (now that every test subdir is being migrated to compile with __WINESRC__) > > Did that restrict us from using single naming scheme? > > Personally I don't see any point in that. The tests are not forced to > use A/W API suffixes, that's done on purpose. Is the purpose gone now? S.

2 1

Re: [07/23] user32/tests: Fix DDE tests compilation with __WINESRC__ defined.
by Marvin Oct. 23, 2013

Oct. 23, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2955 Your paranoid android. === w864 (64 bit dde) === Timeout

1 0

Re: [02/23] user32/tests: Fix class tests compilation with __WINESRC__ defined.
by Marvin Oct. 23, 2013

Oct. 23, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2950 Your paranoid android. === w864 (32 bit class) === class.c:692: Test failed: Windows should be Unicode

1 0

Re: [01/23] user32/tests: Fix broadcast tests compilation with __WINESRC__ defined.
by Marvin Oct. 23, 2013

Oct. 23, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2949 Your paranoid android. === w864 (64 bit broadcast) === The test timed out

1 0

Re: comdlg32/tests: Use BOOL type where appropriate
by Marvin Oct. 23, 2013

Oct. 23, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2943 Your paranoid android. === w2008s64 (64 bit filedlg) === No test summary line found

1 0

Re: [PATCH 5/6] user32/tests: Test SetUserObjectInformation for invisible winstation.
by Marvin Oct. 22, 2013

Oct. 22, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2941 Your paranoid android. === w2008s64 (32 bit winstation) === winstation.c:927: Test failed: unexpected foreground window 0001004E

1 0

Mono Update
by Alistair Leslie-Hughes Oct. 22, 2013

Oct. 22, 2013

Hi, wine-mono hasn't been updated in nearly a year. Should it be time to consider a new release? Thoughts. Best Regards Alistair Leslie-Hughes

2 2

Re: comctl32/tests: Preparation for switching __WINESRC__ on
by Marvin Oct. 22, 2013

Oct. 22, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2934 Your paranoid android. === wvista (32 bit listview) === listview.c:5043: Test failed: NM_HOVER allow test: the msg sequence is not complete: expected 0087 - actual 0000 listview.c:5048: Test failed: NM_HOVER block test: the msg sequence is not complete: expected 0087 - actual 0000 === w2008s64 (32 bit listview) === listview.c:5043: Test failed: NM_HOVER allow test: the msg sequence is not complete: expected 0087 - actual 0000 listview.c:5048: Test failed: NM_HOVER block test: the msg sequence is not complete: expected 0087 - actual 0000 === w7pro64 (32 bit listview) === listview.c:5043: Test failed: NM_HOVER allow test: the msg sequence is not complete: expected 0087 - actual 0000 listview.c:5048: Test failed: NM_HOVER block test: the msg sequence is not complete: expected 0087 - actual 0000 === w864 (32 bit listview) === listview.c:5043: Test failed: NM_HOVER allow test: the msg sequence is not complete: expected 0087 - actual 0000 listview.c:5048: Test failed: NM_HOVER block test: the msg sequence is not complete: expected 0087 - actual 0000 === w2008s64 (64 bit listview) === listview.c:5043: Test failed: NM_HOVER allow test: the msg sequence is not complete: expected 0087 - actual 0000 listview.c:5048: Test failed: NM_HOVER block test: the msg sequence is not complete: expected 0087 - actual 0000 === w7pro64 (64 bit listview) === listview.c:5043: Test failed: NM_HOVER allow test: the msg sequence is not complete: expected 0087 - actual 0000 listview.c:5048: Test failed: NM_HOVER block test: the msg sequence is not complete: expected 0087 - actual 0000

1 0

Re: [PATCH 3/3] msvcrt: Don't output __ptr64 when UNDNAME_NO_MS_KEYWORDS is used
by Marvin Oct. 22, 2013

Oct. 22, 2013

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

1 0

Re: [PATCH 2/3] msvcrt: Output ptr64 when UNDNAME_NO_LEADING_UNDERSCORES flag is used
by Marvin Oct. 22, 2013

Oct. 22, 2013

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

1 0

Re: [PATCH 1/3] msvcrt: Add support for UNDNAME_NO_THISTYPE flag in __unDName
by Marvin Oct. 22, 2013

Oct. 22, 2013

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

1 0

Re: oleaut32: Added a preliminary test, for scale overflow, in VarDecCmp. (try 2) (resend)
by Marvin Oct. 22, 2013

Oct. 22, 2013

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

1 0

Re: oleaut32: Added a preliminary test, for scale overflow, in VarDecCmp. (resend)
by Dmitry Timoshkov Oct. 22, 2013

Oct. 22, 2013

Christopher Cope <ccope3(a)utk.edu> wrote: > --- a/dlls/oleaut32/vartype.c > +++ b/dlls/oleaut32/vartype.c > @@ -5836,7 +5836,9 @@ HRESULT WINAPI VarDecRound(const DECIMAL* pDecIn, int cDecimals, DECIMAL* pDecOu > HRESULT WINAPI VarDecCmp(const DECIMAL* pDecLeft, const DECIMAL* pDecRight) > { > HRESULT hRet; > - DECIMAL result; > + static DECIMAL scaleFactor; Is there a reason to make this variable static? -- Dmitry.

1 0

Re: shlwapi: Test and fix the behaviour of the CopyTo method for file sizes not multiple of the internal buffer size, on SHCreateStreamOnFileEx-returned IStreams.
by Vincent Povirk Oct. 21, 2013

Oct. 21, 2013

We should probably still exit the loop if fewer bytes were read than requested, rather than do another read at the end of the file.

1 0

Re: msvcrt: Make first call to fwrite bufferred
by Piotr Caban Oct. 21, 2013

Oct. 21, 2013

Please ignore this patch, it slows down fwrite on unbuffered FILE's. On 10/21/13 15:43, Piotr Caban wrote: > Without this patch fwrite allocates the buffer on first call and doesn't > use it. > --- > dlls/msvcrt/file.c | 125 > +++++++++++++++++++++++------------------------------ > 1 file changed, 54 insertions(+), 71 deletions(-) > > > > >

1 0

Re: [02/02] d3d8: update locked_rect only if wined3d_surface_map succeeds
by Marvin Oct. 21, 2013

Oct. 21, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2910 Your paranoid android. === w864 (32 bit device) === device.c:2481: Test failed: Expected foreground window 000401A4, got 00010084. device.c:3174: Test failed: Expected wndproc 0x4107a0, got 0x4107a0. device.c:4029: Test failed: pBits changed on double lock. device.c:4030: Test failed: Pitch changed on double lock.

1 0

Re: [23/23] kernel32/tests: Enable kernel32 tests compilation with __WINESRC__ defined.
by Marvin Oct. 21, 2013

Oct. 21, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2908 Your paranoid android. === wxppro (32 bit) === No test summary line found === wvista (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7pro64 (32 bit) === No test summary line found === w864 (32 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found === w7pro64 (64 bit) === No test summary line found === w864 (64 bit) === No test summary line found

1 0

Re: [01/02] d3d9: update locked_rect only if wined3d_surface_map succeeds
by Henri Verbeet Oct. 21, 2013

Oct. 21, 2013

On 21 October 2013 10:46, Lasse Rasinen <lrasinen(a)iki.fi> wrote: > diff --git a/dlls/d3d9/tests/device.c b/dlls/d3d9/tests/device.c > index 02b4174..51835c8 100644 > --- a/dlls/d3d9/tests/device.c > +++ b/dlls/d3d9/tests/device.c > @@ -5402,8 +5402,12 @@ static void test_lockrect_invalid(void) > > hr = IDirect3DSurface9_LockRect(surface, &locked_rect, NULL, 0); > ok(SUCCEEDED(hr), "Failed to lock surface with rect NULL, hr %#x.\n", hr); > + locked_rect.pBits = 0xdeadbeef; > + locked_rect.Pitch = 1; > hr = IDirect3DSurface9_LockRect(surface, &locked_rect, NULL, 0); > ok(hr == D3DERR_INVALIDCALL, "Got unexpected hr %#x.\n", hr); > + ok(locked_rect.pBits == 0xdeadbeef, "pBits changed on double lock.\n"); > + ok(locked_rect.Pitch == 1, "Pitch changed on double lock.\n"); > hr = IDirect3DSurface9_UnlockRect(surface); > ok(SUCCEEDED(hr), "Failed to unlock surface, hr %#x.\n", hr); > This introduces warnings: device.c: In function ‘test_lockrect_invalid’: device.c:5405:23: warning: assignment makes pointer from integer without a cast [enabled by default] device.c:5409:26: warning: comparison between pointer and integer [enabled by default] Also applies to the d3d8 test.

1 0

Re: [03/23] kernel32/tests: Fix console tests compilation with __WINESRC__ defined.
by Marvin Oct. 21, 2013

Oct. 21, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2889 Your paranoid android. === w864 (32 bit console) === console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 18, got 00000138 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 20, got 0000013C console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 21, got 0000014C console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 22, got 00000148 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 23, got 00000144 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 24, got 00000150 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 25, got 00000154 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 26, got 00000158 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 28, got 0000015C console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 29, got 00000160 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 30, got 00000164 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 31, got 00000168 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 32, got 0000016C console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 33, got 00000170 console.c:1421: Test failed: [13] Expected output count to be 0, got 1987557047 console.c:1421: Test failed: [15] Expected output count to be 0, got 1987557047 console.c:1421: Test failed: [18] Expected output count to be 3735928559, got 1987557047 console.c:1664: Test failed: [13] Expected output count to be 0, got 1987557047 console.c:1664: Test failed: [15] Expected output count to be 0, got 1987557047 console.c:1664: Test failed: [18] Expected output count to be 3735928559, got 1987557047 === w864 (64 bit console) === console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 18, got 0000000000000054 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 20, got 0000000000000058 console.c:1113: Test failed: Expected OpenConsoleW to return INVALID_HANDLE_VALUE for index 23, got 0000000000000060

1 0

Re: server: Implement job objects (try 3)
by Alexandre Julliard Oct. 21, 2013

Oct. 21, 2013

Andrew Cook <ariscop(a)gmail.com> writes: > It's been another 3 weeks with zero response. You keep sending more and more versions of the same patches, so it seems clear that this stuff is not ready yet. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [02/23] kernel32/tests: Fix file change notification tests compilation with __WINESRC__ defined.
by Marvin Oct. 21, 2013

Oct. 21, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2888 Your paranoid android. === wvista (32 bit change) === change.c:81: Test failed: Missed notification

1 0

Clang Static analysis
by C.W. Betts Oct. 21, 2013

Oct. 21, 2013

I have been doing a Clang static analysis of Wine on OS X using the one provided at http://clang-analyzer.llvm.org and storing the results on my PogoPlug drive. If someone wants to see the results, please tell me and I'll set up your e-mail. You will need a free PogoPlug account to view them. While the contents are zipped, they expand to about 1.2 GB. They are displayed as basic HTML pages, so you don't need anything special other than a web browser to see the results. Or you could click on this link for the analysis of 1.7.4: http://ppl.ug/ND-7PZ3cSzM/

2 1

Re: shell32: Avoid leaks and add parameter checks in SHCreateShellFolderView[Ex]. (try 2)
by Marvin Oct. 20, 2013

Oct. 20, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2885 Your paranoid android. === w864 (64 bit shlfolder) === shlfolder: unhandled exception c0000005 at 000007F851EBABDC

2 1

Re: shell32: Avoid leaks and add parameter checks in SHCreateShellFolderView[Ex].
by Marvin Oct. 20, 2013

Oct. 20, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2880 Your paranoid android. === w864 (64 bit shlfolder) === shlfolder: unhandled exception c0000005 at 000007F851EBABDC

1 0

Re: shell32: Avoid leaks and add parameter checks in SHCreateShellFolderView[Ex].
by Nikolay Sivov Oct. 20, 2013

Oct. 20, 2013

On 10/20/2013 21:01, Thomas Faber wrote: > + if (0) > + { > + // crash on win7 > + pSHCreateShellFolderViewEx(NULL, NULL); > + pSHCreateShellFolderViewEx(NULL, &psv); > + pSHCreateShellFolderViewEx(&csfv, NULL); > + } Please no cpp comments. > + MAKEFUNC_ORD(SHCreateShellFolderViewEx, 174); > + MAKEFUNC_ORD(SHCreateShellFolderView, 256); These call are exported by name at least on XP, probably 2000 too, so it makes no sense to use ordinals here. > + if (!pSHCreateShellFolderView || !pSHCreateShellFolderViewEx) > + { > + win_skip("SHCreateShellFolderView or SHCreateShellFolderViewEx missing.\n"); > + return; > + } I don't think it's really possible to have *Ex version without non-Ex one. > + hr = SHGetDesktopFolder(&desktop); > + ok(hr == S_OK, "got (0x%08x)\n", hr); > + if (FAILED(hr)) > + { > + skip("No desktop folder\n"); > + return; > + } It's not going to fail, so a ok() test is enough. > + memset(&sfvc, 0, sizeof(sfvc)); > + sfvc.cbSize = sizeof(sfvc); > + sfvc.pshf = desktop; > + psv = (void *)0xdeadbeef; > + hr = pSHCreateShellFolderView(&sfvc, &psv); > + ok(hr == S_OK, "Got 0x%08x\n", hr); > + ok(psv != NULL, "psv = %p\n", psv); > + if (psv && psv != (void *)0xdeadbeef) > + { > + refCount = IShellView_Release(psv); > + ok(refCount == 0, "refCount = %u\n", refCount); > + } It's simpler than that. Set 'psv' to NULL and test for it being set after a call. > + test_SHCreateShellFolderView(); You're testing two calls here, so they probably deserve two separate test functions.

1 0

Re: shell32/tests: Use BOOL type where appropriate
by Marvin Oct. 19, 2013

Oct. 19, 2013

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 https://newtestbot.winehq.org/JobDetails.pl?Key=2879 Your paranoid android. === wxppro (32 bit shlexec) === shlexec.c:1197: Test failed: expected 1 args, got 4 shlexec.c:1538: Test failed: argvA4 expected 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\test file.shlexec', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\TESTFI~1.SHL' shlexec.c:1538: Test failed: argvA4 expected 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\test file.shlexec.', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\TESTFI~1.SHL' shlexec.c:1538: Test failed: argvA4 expected 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\%nasty% $file.shlexec', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\%NASTY~1.SHL' shlexec.c:1538: Test failed: argvA4 expected 'C:/DOCUME~1/winetest/LOCALS~1/Temp/wt1.tmp/test file.shlexec', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\TESTFI~1.SHL' shlexec.c:1538: Test failed: argvA4 expected 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\test file.noassoc.shlexec', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\TESTFI~2.SHL' shlexec.c:1538: Test failed: argvA4 expected 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\masked file.shlexec', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\MASKED~1.SHL' shlexec.c:1538: Test failed: argvA4 expected 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\masked file.shlexec', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\MASKED~1.SHL' shlexec.c:1631: Test failed: argvA4 expected 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\test file.shlexec', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\TESTFI~1.SHL' shlexec.c:1939: Test failed: argvA4 expected 'C:\Documents and Settings\winetest\Local Settings\Temp\wt1.tmp\test file.shlexec', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\TESTFI~1.SHL' shlexec.c:1947: Test failed: argvA4 expected 'C:\Documents and Settings\winetest\Local Settings\Temp\wt1.tmp\test file.shlexec', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\TESTFI~1.SHL' shlexec.c:2250: Test failed: argvA3 expected 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\test file.sde', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\TESTFI~1.SDE' shlexec.c:2250: Test failed: argvA3 expected 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\test file.sde', got 'C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\TESTFI~1.SDE' shlexec.c:2240: Test failed: argcA expected 5, but got 4 === wvista (32 bit shlexec) === shlexec.c:137: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wtC34E.tmp\test file.noassoc") WaitForSingleObject returned 258 shlexec.c:1506: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wtC34E.tmp\test file.noassoc") failed: rc=33 err=2 shlexec.c:1530: Test failed: argvA3 expected 'Open', but key not found or empty shlexec.c:1538: Test failed: argvA4 expected 'C:\Users\winetest\AppData\Local\Temp\wtC34E.tmp\test file.noassoc', but key not found or empty === w2008s64 (32 bit shlexec) === shlexec.c:1538: Test failed: argvA4 expected 'C:/Users/ADMINI~1/AppData/Local/Temp/wt9F4A.tmp/test file.shlexec', got 'C:\Users\Administrator\AppData\Local\Temp\wt9F4A.tmp\test file.shlexec' shlexec.c:2606: Test failed: longPath expected 'C:\Users\ADMINI~1\AppData\Local\Temp\wt9F4A.tmp\test2.exe', got 'C:\Users\Administrator\AppData\Local\Temp\wt9F4A.tmp\test2.exe' shlexec.c:2619: Test failed: longPath expected 'C:\Users\ADMINI~1\AppData\Local\Temp\wt9F4A.tmp\test2.exe', got 'C:\Users\Administrator\AppData\Local\Temp\wt9F4A.tmp\test2.exe' shlexec.c:2631: Test failed: longPath expected 'C:\Users\ADMINI~1\AppData\Local\Temp\wt9F4A.tmp\test2.exe', got 'C:\Users\Administrator\AppData\Local\Temp\wt9F4A.tmp\test2.exe' === w864 (32 bit shlexec) === shlexec.c:137: Test failed: ShellExecute(verb="", file="C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.noassoc") WaitForSingleObject returned 258 shlexec.c:137: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.noassoc") WaitForSingleObject returned 258 shlexec.c:1506: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.noassoc") failed: rc=33 err=2 shlexec.c:1538: Test failed: argvA4 expected 'C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.noassoc', but key not found or empty shlexec.c:137: Test failed: ShellExecute(verb="", file="C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.shlexec.noassoc") WaitForSingleObject returned 258 shlexec.c:137: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.shlexec.noassoc") WaitForSingleObject returned 258 shlexec.c:1506: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.shlexec.noassoc") failed: rc=33 err=2 shlexec.c:1538: Test failed: argvA4 expected 'C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.shlexec.noassoc', but key not found or empty shlexec.c:137: Test failed: ShellExecute(verb="", file="C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.noassoc", params="shlexec "C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\wt4E20.tmp" Exec") WaitForSingleObject returned 258 shlexec.c:137: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.noassoc", params="shlexec "C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\wt4E20.tmp" Exec") WaitForSingleObject returned 258 shlexec.c:2059: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\test file.noassoc", params="shlexec "C:\Users\winetest\AppData\Local\Temp\wt4E1F.tmp\wt4E20.tmp" Exec") succeeded: rc=42 === w2008s64 (64 bit shlexec) === shlexec.c:1538: Test failed: argvA4 expected 'C:/Users/ADMINI~1/AppData/Local/Temp/wtDF85.tmp/test file.shlexec', got 'C:\Users\Administrator\AppData\Local\Temp\wtDF85.tmp\test file.shlexec' shlexec.c:2606: Test failed: longPath expected 'C:\Users\ADMINI~1\AppData\Local\Temp\wtDF85.tmp\test2.exe', got 'C:\Users\Administrator\AppData\Local\Temp\wtDF85.tmp\test2.exe' shlexec.c:2619: Test failed: longPath expected 'C:\Users\ADMINI~1\AppData\Local\Temp\wtDF85.tmp\test2.exe', got 'C:\Users\Administrator\AppData\Local\Temp\wtDF85.tmp\test2.exe' shlexec.c:2631: Test failed: longPath expected 'C:\Users\ADMINI~1\AppData\Local\Temp\wtDF85.tmp\test2.exe', got 'C:\Users\Administrator\AppData\Local\Temp\wtDF85.tmp\test2.exe' === w864 (64 bit shlexec) === shlexec.c:137: Test failed: ShellExecute(verb="", file="C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.noassoc") WaitForSingleObject returned 258 shlexec.c:137: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.noassoc") WaitForSingleObject returned 258 shlexec.c:1506: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.noassoc") failed: rc=33 err=2 shlexec.c:1538: Test failed: argvA4 expected 'C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.noassoc', but key not found or empty shlexec.c:137: Test failed: ShellExecute(verb="", file="C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.shlexec.noassoc") WaitForSingleObject returned 258 shlexec.c:137: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.shlexec.noassoc") WaitForSingleObject returned 258 shlexec.c:1506: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.shlexec.noassoc") failed: rc=33 err=2 shlexec.c:1538: Test failed: argvA4 expected 'C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.shlexec.noassoc', but key not found or empty shlexec.c:137: Test failed: ShellExecute(verb="", file="C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.noassoc", params="shlexec "C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\wt9DA6.tmp" Exec") WaitForSingleObject returned 258 shlexec.c:137: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.noassoc", params="shlexec "C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\wt9DA6.tmp" Exec") WaitForSingleObject returned 258 shlexec.c:2059: Test failed: ShellExecute(file="C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\test file.noassoc", params="shlexec "C:\Users\winetest\AppData\Local\Temp\wt9DA5.tmp\wt9DA6.tmp" Exec") succeeded: rc=42 === w864 (64 bit shlfolder) === shlfolder: unhandled exception c0000005 at 000007F851EBABDC

1 0

Re: server: Implement job objects (try 2)
by Andrew Cook Oct. 18, 2013

Oct. 18, 2013

On 17/10/13 15:11, Andrew Cook wrote: > --- > dlls/kernel32/tests/process.c | 172 ++++++++++++++++++++++- > dlls/ntdll/sync.c | 127 +++++++++++++++-- > server/process.c | 313 > ++++++++++++++++++++++++++++++++++++++++++ > server/process.h | 3 + > server/protocol.def | 33 +++++ > 5 files changed, 636 insertions(+), 12 deletions(-) > > Is there something wrong with this patch?

1 0