- wine-devel - winehq.org

Re: [3/4] ws2_32: Add extended IPX protocol support (try 2)
by Marvin 27 Dec '13

27 Dec '13

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=3866 Your paranoid android. === wxppro (32 bit sock) === sock.c:522: Test failed: oob_server (194): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:522: Test failed: oob_server (750): unexpectedly at the OOB mark: 0 === w2008s64 (64 bit sock) === sock.c:522: Test failed: oob_server (654): unexpectedly at the OOB mark: 0

1 0

Re: loader: bump XP 64-bit to service pack 2
by Qian Hong 27 Dec '13

27 Dec '13

Hi Austin, you forgot the patch? On Sat, Dec 28, 2013 at 4:04 AM, Austin English <austinenglish(a)gmail.com> wrote: > Fixes http://bugs.winehq.org/show_bug.cgi?id=35084 > > (follow up to 0463d01f151fb3d7c7acf26c7628683fefb6c130) > > > -- > -Austin > > -- Regards, Qian Hong - http://www.winehq.org

2 1

Re: [4/4] ws2_32/tests: Fix some test message typos
by Marvin 27 Dec '13

27 Dec '13

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=3861 Your paranoid android. === wxppro (32 bit sock) === sock.c:522: Test failed: oob_server (5a8): unexpectedly at the OOB mark: 0 sock.c:2101: Test failed: Expected 10043, received 10047 sock: unhandled exception c0000005 at 71AB3F3A === wvista (32 bit sock) === sock.c:2101: Test failed: Expected 10043, received 10047 === w2008s64 (32 bit sock) === sock.c:522: Test failed: oob_server (750): unexpectedly at the OOB mark: 0 sock.c:2101: Test failed: Expected 10043, received 10047 === w7pro64 (32 bit sock) === sock.c:2101: Test failed: Expected 10043, received 10047 === w2008s64 (64 bit sock) === sock.c:522: Test failed: oob_server (654): unexpectedly at the OOB mark: 0 sock.c:2101: Test failed: Expected 10043, received 10047 sock: unhandled exception c0000005 at 000007FEFE4C9CD9 === w7pro64 (64 bit sock) === sock.c:2101: Test failed: Expected 10043, received 10047

1 0

Re: [3/4] ws2_32: Add extended IPX protocol support
by Marvin 27 Dec '13

27 Dec '13

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=3860 Your paranoid android. === wxppro (32 bit sock) === sock.c:522: Test failed: oob_server (c0): unexpectedly at the OOB mark: 0 sock.c:2101: Test failed: Expected 10043, received 10047 sock: unhandled exception c0000005 at 71AB3F3A === wvista (32 bit sock) === sock.c:2101: Test failed: Expected 10043, received 10047 === w2008s64 (32 bit sock) === sock.c:522: Test failed: oob_server (768): unexpectedly at the OOB mark: 0 sock.c:2101: Test failed: Expected 10043, received 10047 === w7pro64 (32 bit sock) === sock.c:522: Test failed: oob_server (578): unexpectedly at the OOB mark: 0 sock.c:2101: Test failed: Expected 10043, received 10047 === w2008s64 (64 bit sock) === sock.c:522: Test failed: oob_server (7a4): unexpectedly at the OOB mark: 0 sock.c:2101: Test failed: Expected 10043, received 10047 === w7pro64 (64 bit sock) === sock.c:531: Test failed: oob_server (988): not at the OOB mark: 1 sock.c:2101: Test failed: Expected 10043, received 10047

1 0

Re: ws2_32/tests: Add some IPX socket tests
by Bruno Jesus 27 Dec '13

27 Dec '13

On Thu, Dec 26, 2013 at 8:11 PM, Bruno Jesus <00cpxxx(a)gmail.com> wrote: > > It looks like testbot does not support IPX but I manually tested this in XP SP3 and NT4 and the tests are OK. > > These are initial tests to find the problem for bug 6941. Please ignore this patch, I have a better one. Best regards, Bruno

1 0

Re: ws2_32/tests: Add some IPX socket tests
by Marvin 26 Dec '13

26 Dec '13

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=3859 Your paranoid android. === wxppro (32 bit sock) === sock.c:521: Test failed: oob_server (c8): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:521: Test failed: oob_server (750): unexpectedly at the OOB mark: 0 === w2008s64 (64 bit sock) === sock.c:521: Test failed: oob_server (654): unexpectedly at the OOB mark: 0

1 0

Re: msxml3/tests: Constify some character strings
by Marvin 26 Dec '13

26 Dec '13

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=3855 Your paranoid android. === wxppro (32 bit domdoc) === domdoc.c:9860: Test failed: got 00244F94

1 0

Implementing support for MFPlat.dll and MFReadWrite.dll
by Alexandre Bique 25 Dec '13

25 Dec '13

Hi, I'm trying to make Ableton Live works better with wine, and as stated in this bug: https://bugs.winehq.org/show_bug.cgi?id=35105 setting wine version to win8 will make Ableton Live crash. I first though that it was an issue with the OpenFileDialog being replaced by IFileDialog because it was something that changed and it was visible, but after second thought, I'm thinking about something else. I noticed that ableton tries to load these libraries: err:module:import_dll Library MFReadWrite.dll (which is needed by L"C:\\users\\Public\\Application Data\\Ableton\\Live 9 Suite\\Program\\VideoExportMMF.dll") not found err:module:import_dll Library MFPlat.DLL (which is needed by L"C:\\users\\Public\\Application Data\\Ableton\\Live 9 Suite\\Program\\VideoExportMMF.dll") not found and they're part of Microsoft Media Foundation ... And just after IFileDialog returns with valid data, the application crash and we can see on the output: fixme:commdlg:IServiceProvider_fnQueryService Interface {e07010ec-bc17-44c0-97b0-46c7c95b9edc} requested from unknown service {e07010ec-bc17-44c0-97b0-46c7c95b9edc} fixme:shell:ViewModeToListStyle ViewMode 0 not implemented fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1026, a003, 0, 0x23d5b8) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1026, a004, 0, 0x23d5b8) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1025, a003, 1, 0x23d5b8) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1025, a004, 1, 0x23d5b8) fixme:nstc:NSTC2_fnSetControlStyle2 mask & style (0x00000004) contains unsupported style(s): 0x00000004 fixme:commdlg:IServiceProvider_fnQueryService Interface {e07010ec-bc17-44c0-97b0-46c7c95b9edc} requested from unknown service {e07010ec-bc17-44c0-97b0-46c7c95b9edc} fixme:shell:ViewModeToListStyle ViewMode 0 not implemented fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1026, a003, 0, 0x23d248) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1026, a004, 0, 0x23d248) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1025, a003, 1, 0x23d248) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1025, a004, 1, 0x23d248) fixme:shell:IShellBrowser_fnOnViewWindowActive stub, 0xea510 (0x1574fa60) fixme:commdlg:IServiceProvider_fnQueryService Interface {e07010ec-bc17-44c0-97b0-46c7c95b9edc} requested from unknown service {e07010ec-bc17-44c0-97b0-46c7c95b9edc} fixme:shell:ViewModeToListStyle ViewMode 0 not implemented fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1026, a003, 0, 0x23d3a8) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1026, a004, 0, 0x23d3a8) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1025, a003, 1, 0x23d3a8) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1025, a004, 1, 0x23d3a8) fixme:shell:IShellBrowser_fnOnViewWindowActive stub, 0xea510 (0xef860) fixme:commdlg:IServiceProvider_fnQueryService Interface {e07010ec-bc17-44c0-97b0-46c7c95b9edc} requested from unknown service {e07010ec-bc17-44c0-97b0-46c7c95b9edc} fixme:shell:ViewModeToListStyle ViewMode 0 not implemented fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1026, a003, 0, 0x23d3a8) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1026, a004, 0, 0x23d3a8) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1025, a003, 1, 0x23d3a8) fixme:shell:IShellBrowser_fnSendControlMsg stub, 0xea510 (2, 1025, a004, 1, 0x23d3a8) fixme:shell:IShellBrowser_fnOnViewWindowActive stub, 0xea510 (0xeb240) fixme:dbghelp:elf_search_auxv can't find symbol in module So what do you think? Is MFPlat.dll and MFReadWrite.dll a good candidate? If so, how to implement the library? What are the guidelines? Thanks and happy Christmas, -- Alexandre Bique

2 1

Re: [PATCH] ddraw: add dsurface dimension tests, try 5
by Patrick Rudolph 25 Dec '13

25 Dec '13

How much physical memory does each test VM have ? more than 2 GByte ? On 64bit Windows I should be able to allocate 2GByte of virtual memory using the pagefile, shouldn't I ? Regards, Patrick Am 2013-12-14 13:10, schrieb Marvin: > 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=3756 > > Your paranoid android. > > > === w2008s64 (64 bit ddraw4) === > ddraw4.c:5910: Test failed: Creating an offscreen plain surface with > width 0x2001 and height 0xffff returned 8007000e > > === w7pro64 (64 bit ddraw4) === > ddraw4.c:5910: Test failed: Creating an offscreen plain surface with > width 0x2001 and height 0xffff returned 8007000e > > === w2008s64 (64 bit ddraw2) === > ddraw2.c:5313: Test failed: Creating an offscreen plain surface with > width 0x2001 and height 0xffff returned 8007000e > > === w7pro64 (64 bit ddraw2) === > ddraw2.c:5313: Test failed: Creating an offscreen plain surface with > width 0x2001 and height 0xffff returned 8007000e > > === w2008s64 (64 bit ddraw1) === > ddraw1.c:4254: Test failed: Creating an offscreen plain surface with > width 0x2001 and height 0xffff returned 8007000e > > === w7pro64 (64 bit ddraw1) === > ddraw1.c:4254: Test failed: Creating an offscreen plain surface with > width 0x2001 and height 0xffff returned 8007000e > > === w2008s64 (64 bit ddraw7) === > ddraw7.c:5804: Test failed: Creating an offscreen plain surface with > width 0x2001 and height 0xffff returned 8007000e > > === w7pro64 (64 bit ddraw7) === > ddraw7.c:5804: Test failed: Creating an offscreen plain surface with > width 0x2001 and height 0xffff returned 8007000e

2 1

Re: infosoft/tests: Constify a character string
by Marvin 24 Dec '13

24 Dec '13

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=3827 Your paranoid android. === wvista (32 bit infosoft) === infosoft.c:183: Test failed: failed infosoft.c:197: Test failed: failed === w2008s64 (32 bit infosoft) === infosoft.c:183: Test failed: failed infosoft.c:197: Test failed: failed === w7pro64 (32 bit infosoft) === infosoft.c:183: Test failed: failed infosoft.c:197: Test failed: failed === w2008s64 (64 bit infosoft) === infosoft.c:183: Test failed: failed infosoft.c:197: Test failed: failed === w7pro64 (64 bit infosoft) === infosoft.c:183: Test failed: failed infosoft.c:197: Test failed: failed

1 0

COMDLG32: native color picker on mac os x
by Žiga Željko 23 Dec '13

23 Dec '13

Hello, I have made a patch for comdlg32 on Mac OS X that replaces Wine's own color picker dialog with the native one. Bellow are the sources for colordlg.c, cocoa_colordlg.m and Makefile.in (without comments). -------------------- colordlg.c -------------------- static BOOL ChooseColor_CocoaCommon(COLORREF *color, BOOL init); BOOL WINAPI ChooseColorW( CHOOSECOLORW *lpChCol ) { if (!lpChCol) return FALSE; return ChooseColor_CocoaCommon(&lpChCol->rgbResult, lpChCol->Flags & CC_RGBINIT); } BOOL WINAPI ChooseColorA( LPCHOOSECOLORA lpChCol ) { if (!lpChCol) return FALSE; return ChooseColor_CocoaCommon(&lpChCol->rgbResult, lpChCol->Flags & CC_RGBINIT); } struct RGBColor { unsigned short red; unsigned short green; unsigned short blue; }; int cocoa_run_color_dialog_modal(struct RGBColor *color); static BOOL ChooseColor_CocoaCommon(COLORREF *color, BOOL init) { struct RGBColor rgb = { 0, 0, 0 }; if (init) { rgb.red = GetRValue(*color) * 257; rgb.green = GetGValue(*color) * 257; rgb.blue = GetBValue(*color) * 257; } BOOL ret = cocoa_run_color_dialog_modal(&rgb); if (ret) *color = RGB(rgb.red / 257, rgb.green / 257, rgb.blue / 257); return ret; } -------------------- cocoa_colordlg.m -------------------- #import <AppKit/AppKit.h> #import <Carbon/Carbon.h> int cocoa_run_color_dialog_modal(RGBColor *color) { __block int ret = 0; void (^block)(void) = ^{ ret = GetColor((Point){ 0, 0 }, (const unsigned char *)"Color", color, color); }; if ([NSThread isMainThread]) block(); else dispatch_sync(dispatch_get_main_queue(), block); return ret; } -------------------- Makefile.in -------------------- MODULE = comdlg32.dll IMPORTLIB = comdlg32 IMPORTS = uuid shell32 shlwapi comctl32 winspool user32 gdi32 advapi32 DELAYIMPORTS = ole32 EXTRALIBS = -framework AppKit -framework Carbon C_SRCS = \ cdlg32.c \ colordlg.c \ filedlg.c \ filedlg31.c \ filedlgbrowser.c \ finddlg.c \ fontdlg.c \ itemdlg.c \ printdlg.c RC_SRCS = comdlg32.rc SVG_SRCS = \ pd32_collate.svg \ pd32_landscape.svg \ pd32_nocollate.svg \ pd32_portrait.svg OBJC_SRCS = \ cocoa_colordlg.m IDL_R_SRCS = comdlg32_classes.idl @MAKE_DLL_RULES@ ------------------------------------------------------------ Any comments are welcome.

2 1

D3D command stream abandoned?
by Forest 23 Dec '13

23 Dec '13

I haven't seen any news of the command stream lately. The last thing I read was the mention of "more preparation work" in the 1.7.4 release announcement. Has the project been abandoned? I maintain a wine build for gamers, and currently have it frozen at version 1.7.1 with Stefan's September 2 command stream patches, because they seem to boost performance quite a bit for some folks. I'd love to get something more mature into my users' hands if it's available.

2 1

Re: add japanese man page(try 2)
by Akihiro Sagawa 23 Dec '13

23 Dec '13

On Fri, 20 Dec 2013 00:00:38 +0900, Akira Nakagawa wrote: > Subject: [PATCH] add japanese man page(try 2) Looks mostly fine. Please review following five points. 1. Changes for loader/Makefile.in was forgotten in try 2. 2. There were typos. Double punctuations, 「、、」 (two points) > +CUIの実行可能プログラム(Windows コンソールプログラム)を実行するには、、 > +は単にそれぞれ小さなヘルプメッセージ、、またはバージョン情報を表示して終了します。 3. Please don't use `タイプ' for different meanings. The former should be updated. > +はすべてのdll をロードするのに使用されるdll の上書きとロード順位のタイプを定義します。 > +Wineプロセスのアドレス空間にロードされるライブラリには現在2つのタイプがあります。 4. You added a space character after almost half-width characters, but some points not updated. For instance, you might need to add a space character after `X11'. > 使用するX11のディスプレイを指定します。 And you didn't insert a space character *before* a half-width character. Are they intentional? 5. There is still `.UE .' in the document. > +多くのアプリケーションのステータス報告が > +.UR http://appdb.winehq.org > +.B Wine Application Database > +にあります。 > +.UE . This should be: 多くのアプリケーションのステータス報告が .UR http://appdb.winehq.org .B Wine Application Database .UE にあります。 Regards, Akihiro Sagawa

1 0

Re: [2/4] taskschd: Add registration for TaskScheduler interfaces.
by Alexandre Julliard 23 Dec '13

23 Dec '13

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > +[ > + threading(both), > + progid("Schedule.Service.1"), > + vi_progid("Schedule.Service"), > + uuid(0f87369f-a4e5-4cfc-bd3e-73e6154572dd) > +] > +coclass TaskService { interface ITaskService; } This should go in the public header, with the correct name. It's also supposed to be a typelib. -- Alexandre Julliard julliard(a)winehq.org

1 0

ldd for wine dll- Sorry for preview spell errors,
by 逸天不羁 23 Dec '13

23 Dec '13

hello every one, I have write a application just like ldd of GNU/Linux, I don't how to push it to the upstream. Here is the patchs.

3 2

Re: [PATCH] oleacc: Added DllGetClassObject() stub
by 中川祥 22 Dec '13

22 Dec '13

You need to add registry for it. And why don't you implement it? Some other dlls did it. 2013/12/22, Nikolay Sivov <nsivov(a)codeweavers.com>: > --- > dlls/oleacc/main.c | 6 ++++++ > dlls/oleacc/oleacc.spec | 1 + > 2 files changed, 7 insertions(+) > > >

2 1

ldd for wine dll---cpp codes removed
by 逸天不羁 22 Dec '13

22 Dec '13

hello, Every one , although we have the winedump, this little tool can be useful sometime. And I have remove all the cpp codes .

1 0

ldd for wine dll
by 逸天不羁 21 Dec '13

21 Dec '13

hell every one, I have write a application just like ldd of GNU/Linux, I don't how to push it to the upstream. Here is the patchs.

2 1

Fwd: ldd for wine dll
by David Quintana (gigaherz) 21 Dec '13

21 Dec '13

(forwarding to the list) ---------- Forwarded message ---------- From: David Quintana (gigaherz) <gigaherz(a)gmail.com> Date: 21 December 2013 12:16 Subject: Re: ldd for wine dll To: 逸天不羁 <yitianbuji(a)qq.com> Read this guide: http://wiki.winehq.org/SubmittingPatches On 21 December 2013 12:12, 逸天不羁 <yitianbuji(a)qq.com> wrote: > hell every one, > I have write a application just like ldd of GNU/Linux, I don't how to push > it to the upstream. Here is the patchs. > > > >

1 0

Re: [3/5] ntdll: Allow passing NULL buffer to printf functions
by Alexandre Julliard 20 Dec '13

20 Dec '13

Sebastian Lackner <sebastian(a)fds-team.de> writes: > @@ -72,7 +73,12 @@ static inline int pf_output_stringW( pf_output *out, LPCWSTR str, int len ) > > if( len < 0 ) > len = strlenW( str ); > - if( out->unicode ) > + if (!out->buf.X) > + { > + out->used += len; > + return len; > + } > + else if (out->unicode) That's not correct for Unicode conversions. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 1/3] port: MSVC provides a correct getenv prototype.
by Stefan Dösinger 19 Dec '13

19 Dec '13

Am 19.12.2013 um 15:23 schrieb Jonas Maebe <jonas.maebe(a)elis.ugent.be>: > Shouldn't the title of this patch read "getopt" instead of "getenv"? Uh, now that you mention it, the title isn’t quite right. It should be more like "port: MSVC does not provide a conflicting getopt prototype." - It doesn’t provide a getopt prototype at all. The stdlib.h include is needed for getenv, which is used in the file. I misread the "getopt" in the comment as "getenv" on my quick read. (And yes, I did wonder how this code is supposed to work without defining getenv at all, but my conclusion was that maybe a warning about undefined getenv was considered better than a compile error. It makes a lot more sense with a conflicting getopt.) I took the liberty to CC wine-devel on my reply.

1 0

Re: taskschd: Add new dll.
by Saulius Krasuckas 18 Dec '13

18 Dec '13

* On Tue, 17 Dec 2013, Dmitry Timoshkov wrote: > 4 files changed, 123 insertions(+) > create mode 100644 dlls/taskschd/Makefile.in > create mode 100644 dlls/taskschd/taskschd.c > create mode 100644 dlls/taskschd/taskschd.spec Could you please tell what app does need it? I find zero bugs with the bugzilla query. [*] S. [*] http://bugs.winehq.org/buglist.cgi?query_format=advanced&longdesc=taskschd&…

3 3

Wine + ICC (Intel XE Compiler)
by jordan 18 Dec '13

18 Dec '13

Hey List, I've been playing around with ICC and i am curious if anyone has instructions and/or Patches for building Wine using Intel's XE Compiler?? ...I'm using the latest version; icc version 14.0.1 (gcc version 4.8.0 compatibility) I've noticed older link on winehq; http://wiki.winehq.org/icc ... It seems he was able to get wine32 to build on x86_64, but obviously, 2008 was a little early for wine64 / ICC tests... Currently, it doesn't get to far through configure; checking for gcc... icc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether icc accepts -g... yes checking for icc option to accept ISO C89... none needed checking whether we are using the GNU C++ compiler... yes checking whether icpc accepts -g... yes checking for cpp... cpp checking whether icc supports __builtin_ms_va_list... no configure: error: You need gcc >= 4.4 to build Wine as 64-bit. (and then it terminates). ICC is setup properly on my machine(s), ie: i have used it to compile other packages. (mostly 64bit, but i did test 32bit, which worked fine too). Anyway, If anyone has any tips and/or patches they could share, I would be very grateful / interested. :) ... Jordan

3 4

Launchpad project for Wine
by Tae Wong 18 Dec '13

18 Dec '13

There's a Launchpad project for Wine: https://launchpad.net/wine But there's a misspelling: ...a compatability layer... It says compatability instead of compatibility. The account https://launchpad.net/~seotaewong40 has been disabled. How to enable this account to file bugs? When trying to visit the page, it says: Page gone. There’s no page with this address in Launchpad. If this is blocking your work, let us know by asking a question at Launchpad Support . Otherwise, complain to the maintainers of the page that linked here.

2 1

Travel sponsorship for Wine to FOSDEM
by Jeremy White 17 Dec '13

17 Dec '13

Folks, I neglected to put this out there, but the Wine party fund is able to provide travel sponsorships for Wine contributors (where contributors is not limited to programmers, and can be fairly loosely defined). If you are interested in such a sponsorship, please write me privately. We could still use some novel presentations in our dev room; so if you want to get sponsored to come talk about Wine users or pitch the use of Wine on the lunar lander, I'd be delighted by the combination. Cheers, Jeremy

1 0

Re: [PATCH] msxml3: Store document url in properties so every instance could see it
by Marvin 17 Dec '13

17 Dec '13

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=3762 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: taskschd: Add new dll.
by Nikolay Sivov 17 Dec '13

17 Dec '13

On 12/17/2013 13:30, Dmitry Timoshkov wrote: > +WINE_CONFIG_DLL(taskschd,,[implib]) Does it really need implib?

1 0

Re: winemenubuilder: Return error for missing link in InvokeShellLinkerForURL function
by Dmitry Timoshkov 16 Dec '13

16 Dec '13

Frédéric Delanoy <frederic.delanoy(a)gmail.com> wrote: > --- a/programs/winemenubuilder/winemenubuilder.c > +++ b/programs/winemenubuilder/winemenubuilder.c > @@ -3030,7 +3030,7 @@ static BOOL InvokeShellLinkerForURL( IUniformResourceLocatorW *url, LPCWSTR link > if ( !link ) > { > WINE_ERR("Link name is null\n"); > - return TRUE; > + return FALSE; > } This doesn't follow the behaviour of other failure cases in this helper. -- Dmitry.

2 1

Re: [PATCH] ddraw: add dsurface dimension tests, try 5
by Stefan Dösinger 15 Dec '13

15 Dec '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 2013-12-14 12:34, schrieb Patrick Rudolph: > + /* Test maximum surface width */ + memset(&desc, 0, > sizeof(desc)); + desc.dwSize = sizeof(desc); + desc.dwFlags = > DDSD_CAPS | DDSD_HEIGHT | DDSD_WIDTH; + desc.ddsCaps.dwCaps |= > DDSCAPS_OFFSCREENPLAIN; + desc.dwHeight = 1; + desc.dwWidth = > 0xffff; + ret = IDirectDraw_CreateSurface(lpDD, &desc, > &dsurface, NULL); + if(!(ddcaps.ddsCaps.dwCaps & > DDSCAPS_VIDEOMEMORY)) + { + ok(ret == > DDERR_INVALIDPARAMS, "Creating an offscreen plain surface with > width 0xffff and height 1 returned %08x\n", ret); + } + else > + { + todo_wine ok(ret == DD_OK, "Creating an offscreen > plain surface with width 0xffff and height 1 returned %08x\n", > ret); + } I found the reason for this behavior. Some drivers seem to have a pitch limit of slightly under 128kb, specifically 131008 bytes. If you use a P8 pixel format here, the test passes on at least my Nvidia machine with this behavior. The same machine still has the 0xffff width limitation. So a 0x10000 width P8 surface isn't allowed, even though the pitch stays below the limit. I guess you could test for the pitch limit by setting DDSD_PITCH, either in CreateSurface, if it works, or pass it to SetSurfaceDesc. I don't think we have to test this unless we know an application that depends on this limitation - which I guess is unlikely because not all Windows drivers have it. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSrZ1sAAoJEN0/YqbEcdMw6S0P/iZxvm5yH7hVoRJySKTtlDdD JB5JgGnG64ghBFX3SNRY38WP5iJT/Sgq2J8ueN2m/J5r83Ms7gtVz/2e0dm8ENgs MI2ln+0rXeC9vIAXNaM3VRTLKoOKql3sYSXEGvQNPtS56kvENz/2Mgfk00d6MfTJ 7tVtrgqfewR4KUjRzPnVDZO1Ofu4SiILFIYV75qAPO0ZQbEpqJGhxxJqoBYhpcpR GM9bD+4zajM9NJhZR4w3G8p23JVpUySso3xEXiV9RL16SvODnedf5o69wEB6ihyl zbSoyvntqDDiFkUSbrjPdu89TNVJ9vYRQsxEm/56P6DtN9SqHkQpQVBAFC370Tbd fAHQQWVnG0yr7/YAhRcB5+8hoyeX7H8p5Vk8nbcYNNQouKFVLMmRICGoaRLHPnqC 7cnrXw6/fL583FgsnevuX/n+ENsqwa7OkkVzlNLm746SPTnF1I+14ERHe8ADh25l 3ushOkUCJvQISDmRAzV0T4m8if6ljMPIIfMCPR0xNDTAFt5tBcYaHexw0GOh9UCD jGp9d6NYRuEf49jH3oYwVcdleGY8e1HrhT/N/s8pbMIWctgu/1s3RAERy5DEd8Hl otUR9I4DbCD4qWcaF3tW1K3syL8E3UTYjzlQ1GBlc018MsaIfebH7ds44oE1tVgk m0KcynUFCzigbONka3IB =XDx8 -----END PGP SIGNATURE-----

1 0

Re: add japanese man page
by Akihiro Sagawa 15 Dec '13

15 Dec '13

On Thu, 12 Dec 2013 16:57:58 +0900, Akira Nakagawa wrote: > diff --git a/loader/wine.ja.UTF-8.man.in b/loader/wine.ja.UTF-8.man.in > new file mode 100644 > index 0000000..8c6f851 > --- /dev/null > +++ b/loader/wine.ja.UTF-8.man.in Great work! Updated man page is almost good. This includes much improvements from previous one. But some issues are remain. Typical issue is line length. Because groff, used for formatting man-pages, doesn't handle Japanese non-spacing line-breaking well. I have two suggestions about this: 1. Insert a space character between half-width character and full-width one. e.g. Windows のプログラムを Unix で実行します 2. Insert a space character between English words. e.g. Windows コンソールプログラム Other (mistranslation, nit-picking) issues as follows. > +.SH 説明 > +.B wine > +は引数に指定されたDOS、Windows > +3.X、 Win32またはWin64の実行可能なプログラムを読み込んで実行します(64bitシステム上の場合)。 How about reorder parenthesis text near by Win64? I feel a reader can't find where the end parenthesis depends on. In other words, he or she can't find out what application can be run on 32-bit systems. Please use 「64-bit」 like others, but I prefer 「64 bit」(without hyphen) or 「64ビット」(translate `bit' to Japanese transcription). > +CUIの実効可能プログラム(Windowsコンソールプログラム)を実行するには, > +.BR wine の代わりに > +.B wineconsole > +を使用してください。 Conversion error: 実効可能 -> 実行可能 Last comma, 「実行するには,」, should be Japanese punctuation mark. > +これはすべての出力を別々のウィンドウに出力します(これを実行するには > +X11が必要です)。 CUIプログラム用の > +.B wineconsole > +は非常に制限されたコンソールのサポートを提供するだけで、 > +プログラムはおそらく正しく機能しないでしょう。 The original text says `Not using wineconsole... ', but your translation says `wineconsole for CUI programs provides...'. > +.PP > +.B --help > +または > +.B --version > +だけを引数として実行した場合、 > +.B wine > +はただ小さなヘルプメッセージまたはバージョン情報をそれぞれ表示して終了します。 A reader might not get a meaning at the first reading. Because 「ただ」(simply)～「表示して」(print) are separated in the translation. > +.B wine > +を実行する際にコマンドラインの最後尾に実行するプログラムの引数を付け加えることで、 > +そのプログラムに引数を渡すことができます。 > +(例えば: \fIwine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT\fR). > +注:シェル上でWineを実行する際には、 > +エスケープシーケンス「\(rs」(とスペース)を付ける必要があります。 I think this is misleading. The original text mentions the need for escaping, and that is for special characters and spaces (because this might not be a character). Your translation just says need to add escape-sequence '\' (and spaces). > +.TP > +.B WINESERVER > +.B wineserver > +のパスと名前を指定します。 > +binary. これを指定しない場合、Wineは > +.IR @bindir@/wineserverを > +ロードしようとします。 Delete `binary.', please. > +.TP > +.B WINELOADER > +が新しいWindowsプロセスを立ち上げるためには > +.B wine > +のバイナリのパスと名前を指定します。 This text is unnatural and wrong. > .PP > .I クラス > はオプションで、次のいずれかです。 > .BR err > .BR warn > .BR fixme > .BR trace Please add punctuations for each keywords, and use a column at the end of the sentence. > +If > +.I クラス > +が指定されない場合、指定されたチャンネルのすべてのデバッグメッセージが表示されるようになります。それぞれのチャンネルは固有のWineのメッセージを出力します。 Please delete `If.' line. > +.TP > +WINEDEBUG=warn+dll,+heap > +はDLLの警告メッセージとすべてのヒープメッセージ有効にします。 > +.br メッセージ有効に --> メッセージを有効に > +.TP > +.B WINEDLLOVERRIDES > +はすべてのdllをロードするのに使用されるdllの上書きとロード命令のタイプを定義します。 You might think there is a load instruction type, but the original just says [override type] and [load order]. So, there is no types for load order. Additionally, in this case, I prefer to use 「ロード順序(=load sequence)」 for translating `load order', not 「ロード命令(=load directive)」. > +現在2つのタイプのWineプロセスのアドレス空間にロードされるライブラリがあります。 A reader might not get a meaning at the first reading. How about reordering like this? 「Wineプロセスのアドレス空間にロードされるライブラリには現在2つのタイプがあります。」 > +つまり、ネイティブのwindows dll.RI ( native ") とWine内蔵版dlls (" builtin )です。 This line needs to break before `.RI'. Plural word (dlls) is not common in Japanese text, please use `Wine内蔵版dll'. > +Ｗindowsのサポートするアーキテクチャを指定します。この変数は The first `W' is full-width form, please use half-width form like others. > +.TP > +OSSのサウンドドライバを設定する変数 A colon is needed at the end of this line. > .SH 製作者 > Wineは多くの開発者の働きによって成り立っています。製作者を一覧するには、ソースディストーションの最上層ディレ > クトリにあるテキストファイル > .I AUTHORS > を参照してください。 Unknown word: ディストーション (distortion?) Please reconsider to use this word. > +WineはLGPLライセンスの下で発布されています。ライセンスのコピーは Less commonly usage. Please consider to use following words, `発布' (distribute) -> `配布' `コピー' (copy) -> `写し' > +バグ報告は > +.UR http://bugs.winehq.org > +.B Wine bug tracker > +で行えます。 > +.UE . There is a redundant dot at the end of the sentence. How about changing as following: バグ報告は .UR http://bugs.winehq.org .B Wine bug tracker .UE で行えます。 > +最新のバージョンの > +.B wine > +はWineHQ > +.UR http://www.winehq.org/ > +.B Wine development headquarters > +から入手できます。 > +.UE . ditto. Regards, Akihiro Sagawa

1 0

Re: [PATCH] ddraw: add dsurface dimension tests, try 5
by Stefan Dösinger 14 Dec '13

14 Dec '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Thanks for your persistence on this issue. I'll try to run those tests on some of my Windows machines to spot any card / driver dependent results. Some of your tests could be fragile, but I'll have a better opinion on that after trying them myself. Overall, you could reduce the number of lines of code here by organizing the test data in a table. Try something like static const struct { DWORD flags, width, height; HRESULT expect_hr; } test_data[] = { {DDSD_HEIGHT, 0, 128, DDERR_INVALIDPARAMS}, {DDSD_WIDTH, 128, 0, DDERR_INVALIDPARAMS}, {DDSD_WIDTH | HEIGHT, 128, 128, DD_OK}, {DDSD_WIDTH | HEIGHT, 0, 128, DDERR_INVALIDPARAMS}, {DDSD_WIDTH | HEIGHT, 128, 0, DDERR_INVALIDPARAMS}, etc. } Some things, like the video memory size exhaustion checks and the primary surface size checks are hard to handle this way. You can keep them in separate code blocks. Here are a few more issues, mostly minor style points: > + IDirectDrawSurface *dsurface = NULL; + IDirectDraw *lpDD; Please don't use the hungarian notation. I recommend to use the names ddraw and surface. > + ok(ret == DDERR_INVALIDPARAMS, "Creating an offscreen plain surface without a size info returned %08x (dsurface=%p)\n", ret, dsurface); This is a minor issue, but please add interpunctuation for consistency's sake. I don't think there's a reason to write dsurface here, other tests already establish that it should be NULL in case of an error. > + if(dsurface) + { + trace("Surface at %p\n", > dsurface); + IDirectDrawSurface_Release(dsurface); + > dsurface = NULL; + } The trace looks like it is a debugging leftover. > + /* Sanity check */ + memset(&desc, 0, sizeof(desc)); + > desc.dwSize = sizeof(desc); + desc.dwFlags = DDSD_CAPS | > DDSD_HEIGHT | DDSD_WIDTH; + desc.ddsCaps.dwCaps |= > DDSCAPS_OFFSCREENPLAIN; + desc.dwHeight = 128; + desc.dwWidth > = 128; + ret = IDirectDraw_CreateSurface(lpDD, &desc, &dsurface, > NULL); This isn't really necessary, if surface creation fails here many other tests wouldn't work. If you use a test data table like described above I'd leave it in to make sure the test loop works properly. > + desc.dwHeight = 1; + desc.dwWidth = 0xffff; + ret = > IDirectDraw_CreateSurface(lpDD, &desc, &dsurface, NULL); + > if(!(ddcaps.ddsCaps.dwCaps & DDSCAPS_VIDEOMEMORY)) + { + > ok(ret == DDERR_INVALIDPARAMS, "Creating an offscreen plain surface with width 0xffff and height 1 returned %08x\n", ret); > + } + else + { + todo_wine ok(ret == DD_OK, > "Creating an offscreen plain surface with width 0xffff and height 1 returned %08x\n", ret); > + } You can drop the curly brackets here, the existing code doesn't use them for single-line code blocks. (Well, mostly. It's not entirely consistent). I don't really like the DDSCAPS_VIDEOMEMORY check. I'll see how my Windows boxes behave, then we'll know if there's any deeper relationship between software-only ddraw and a maximum surface size. > + ret = IDirectDraw_CreateSurface(lpDD, &desc, &dsurface, > NULL); + todo_wine ok(ret == DDERR_INVALIDPARAMS, "Creating an > offscreen plain surface with width 0x10000 and height 1 returned %08x\n", ret); > + if(dsurface) + { + > IDirectDrawSurface_Release(dsurface); + dsurface = NULL; + > } If all possible paths expect a failure from CreateSurface, there's no need to try to release the surface. Just leak it, the test fails anyway. > + ret = IDirectDraw_SetCooperativeLevel(lpDD, NULL, > DDSCL_NORMAL); + ok(ret == DD_OK, "SetCooperativeLevel failed > with %08x\n", ret); I don't think this is needed. Also, is there a reason why you're not passing the window to the first SetCooperativeLevel call? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSrIlaAAoJEN0/YqbEcdMw48UP/R686XgOaYmgwxP23u5AUpM2 +zemL+zkTAmQdLXA0yrFTmXvQcEvJtd1j7Pbg32hCh1P4X27ygBO5L+XJ4oxfTwH ymYYyIJsU96iTIDqojOlqzAvQ/Z/aibIfrfmviWx0LIClUymu5+VWYgYmONqbf5p QAkVrAV12DRrQq1sJPXoqSZDaDvtsuj5hjuZbGdZBoP0vJygl+yZXgxdNsrfDh3l TIRrYyETdWdCFjjxEbJyFeB6lrFweAHOel54cuvAlGjErlSczdj8oCMGoHHGtnNr JOD5dK0LI1o9ngkbmIMSHfRo4Sk6Ug6476B9zNR/fETRXsBEPCVQfWoUIV3h0RI0 RjX5NMFRHANYRjXSQd8yXcpdyNWYONu0BhyBrMnHBNln+CpXyUJ8PM0nMptnVSKD 1fWzQfnQNnaklxYuHVvSuVctOPLmbf5PIHNSE333Xj0ddDA2uCtEzOkSH1aMStjV TMZUa7ggY0wCjeLP1NKOY6jN7ExhANx8ItzXn4h8n9eWNMyqJXi9kpfiVGJA9/v8 /Xmi2nWivBBWUh8qq5nPUGnWcLgeKuvFTobGq3jUbCYEf3/T7sZz58xuFdAp/xUt Yzg2ztvP9DUi8BuJuk51c0dtujgtIRMKkNCG/ISe7za2QhGloAGs0T/LWdUmrTxo ++uOj6zpdlFWCapAen6e =13rk -----END PGP SIGNATURE-----

1 1

Re: [PATCH] ddraw: add dsurface dimension tests, try 5
by Marvin 14 Dec '13

14 Dec '13

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=3756 Your paranoid android. === w2008s64 (64 bit ddraw4) === ddraw4.c:5910: Test failed: Creating an offscreen plain surface with width 0x2001 and height 0xffff returned 8007000e === w7pro64 (64 bit ddraw4) === ddraw4.c:5910: Test failed: Creating an offscreen plain surface with width 0x2001 and height 0xffff returned 8007000e === w2008s64 (64 bit ddraw2) === ddraw2.c:5313: Test failed: Creating an offscreen plain surface with width 0x2001 and height 0xffff returned 8007000e === w7pro64 (64 bit ddraw2) === ddraw2.c:5313: Test failed: Creating an offscreen plain surface with width 0x2001 and height 0xffff returned 8007000e === w2008s64 (64 bit ddraw1) === ddraw1.c:4254: Test failed: Creating an offscreen plain surface with width 0x2001 and height 0xffff returned 8007000e === w7pro64 (64 bit ddraw1) === ddraw1.c:4254: Test failed: Creating an offscreen plain surface with width 0x2001 and height 0xffff returned 8007000e === w2008s64 (64 bit ddraw7) === ddraw7.c:5804: Test failed: Creating an offscreen plain surface with width 0x2001 and height 0xffff returned 8007000e === w7pro64 (64 bit ddraw7) === ddraw7.c:5804: Test failed: Creating an offscreen plain surface with width 0x2001 and height 0xffff returned 8007000e

1 0

Re: Ken Thomases : user32: Respect monitor work area when sizing or moving a top-level window.
by Ken Thomases 14 Dec '13

14 Dec '13

Hi Alexandre, This doesn't do the same thing as what I submitted. May I ask why you changed it? For instance, you shouldn't be able to drag the title bar even partially behind the menu bar. On Windows, I don't believe you can drag the title bar partially off the top of the screen. I'm certain that, if you position the task bar at the top of the screen, you can't drag the title bar partially behind it, either. (I tested both but my memory of the former isn't certain.) -Ken On Dec 13, 2013, at 12:46 PM, Alexandre Julliard wrote: > Module: wine > Branch: master > Commit: 03f8f85ddae0cb7d7ff85d0478f1d9a77c88b26b > URL: http://source.winehq.org/git/wine.git/?a=commit;h=03f8f85ddae0cb7d7ff85d047… > > Author: Ken Thomases <ken(a)codeweavers.com> > Date: Thu Dec 12 16:49:48 2013 -0600 > > user32: Respect monitor work area when sizing or moving a top-level window. > > This prevents dragging a window's title bar behind a menu bar across the top > of a screen, for example. > > --- > > dlls/user32/winpos.c | 20 ++++++++++++++++++++ > 1 files changed, 20 insertions(+), 0 deletions(-) > > diff --git a/dlls/user32/winpos.c b/dlls/user32/winpos.c > index 22ee290..7cae0ad 100644 > --- a/dlls/user32/winpos.c > +++ b/dlls/user32/winpos.c > @@ -2625,6 +2625,7 @@ void WINPOS_SysCommandSizeMove( HWND hwnd, WPARAM wParam ) > BOOL moved = FALSE; > DWORD dwPoint = GetMessagePos (); > BOOL DragFullWindows = TRUE; > + HMONITOR mon = 0; > > if (IsZoomed(hwnd) || !IsWindowVisible(hwnd)) return; > > @@ -2673,6 +2674,7 @@ void WINPOS_SysCommandSizeMove( HWND hwnd, WPARAM wParam ) > { > parent = 0; > mouseRect = get_virtual_screen_rect(); > + mon = MonitorFromPoint( pt, MONITOR_DEFAULTTONEAREST ); > } > > if (ON_LEFT_BORDER(hittest)) > @@ -2749,6 +2751,24 @@ void WINPOS_SysCommandSizeMove( HWND hwnd, WPARAM wParam ) > pt.y = max( pt.y, mouseRect.top ); > pt.y = min( pt.y, mouseRect.bottom ); > > + if (!parent) > + { > + HMONITOR newmon; > + MONITORINFO info; > + > + if ((newmon = MonitorFromPoint( pt, MONITOR_DEFAULTTONULL ))) > + mon = newmon; > + > + info.cbSize = sizeof(info); > + if (mon && GetMonitorInfoW( mon, &info )) > + { > + pt.x = max( pt.x, info.rcWork.left ); > + pt.x = min( pt.x, info.rcWork.right ); > + pt.y = max( pt.y, info.rcWork.top ); > + pt.y = min( pt.y, info.rcWork.bottom ); > + } > + } > + > dx = pt.x - capturePoint.x; > dy = pt.y - capturePoint.y; > > > >

2 1

Re: wined3d: Ensure wined3d_ftoa() exponent is 2 digits on Windows.
by Henri Verbeet 14 Dec '13

14 Dec '13

On 14 December 2013 06:28, Jonathan Liu <net147(a)gmail.com> wrote: > > This fixes a regression introduced by commit > 12f16f2127ffce9a05eedf008c3aa3732751a7e3 where the returned exponent > is 3 digits on Windows instead of 2 digits which results in rendering > errors. The printf implementation in the Microsoft Visual C runtime > uses three digits for the exponent by default. > If the issue here is that the buffers the callers pass are too small, I think that's what should be fixed, perhaps with a comment added to wined3d_ftoa(). Ideally we wouldn't use fixed size buffers there to begin with though.

1 0

Re: winealsa.drv: midiSeq must be protected by a mutex
by Alexandre Julliard 13 Dec '13

13 Dec '13

Alexandre Bique <bique.alexandre(a)gmail.com> writes: > @@ -95,6 +95,7 @@ static int MODM_NumDevs = 0; > /* this is the total number of MIDI out devices found */ > static int MIDM_NumDevs = 0; > > +static CRITICAL_SECTION midiSeqLock = { NULL, -1, 0, 0, 0, 0 }; Please add debug information like it's done in other places. -- Alexandre Julliard julliard(a)winehq.org

1 0

Bugzilla attachment links arriving with &action=edit
by Bruno Jesus 13 Dec '13

13 Dec '13

Hi all, since the update yesterday all links in emails received from the bugzilla have the action=edit so it's not no longer possible to directly open the attachements. Examples: --- Comment #8 from The Source <xxx(a)mail.ru> --- Created attachment 46837 --> http://bugs.winehq.org/attachment.cgi?id=46837&action=edit Launcher log (local.log) --- Comment #1 from Bruno Jesus <xxx(a)gmail.com> --- Created attachment 46835 --> http://bugs.winehq.org/attachment.cgi?id=46835&action=edit standard output --- Comment #3 from Travis Greenman <xxx(a)cartman-2000.net > --- Created attachment 46833 --> http://bugs.winehq.org/attachment.cgi?id=46833&action=edit Console output, with gl error and nvidia-smi output. Regards, Bruno

8 11

Re: [PATCH 3/5] ddraw: Change surface pitch before width.
by Henri Verbeet 13 Dec '13

13 Dec '13

On 13 December 2013 12:30, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > + switch(hr) > + { > + case WINED3DERR_INVALIDCALL: > + wined3d_mutex_unlock(); > + return DDERR_INVALIDPARAMS; > + default: > + break; /* Go on */ > + } That's called hr_ddraw_from_wined3d(). On its own this patch is perhaps innocent enough, but it looks like this is supposed to make 4/5 safe, in which case that patch ends up depending on a somewhat obscure implementation detail. I think it may be better to merge wined3d_surface_set_mem() into wined3d_surface_update_desc(), at least as far as the public interface is concerned. (And in the long term we really want that to be wined3d_texture_update_desc().)

2 3

Re: [PATCH] ddraw: add dsurface dimension tests, try 4
by Marvin 13 Dec '13

13 Dec '13

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=3751 Your paranoid android. === build (build) === Patch failed to apply

1 0

Firefox says mirrors.ibiblio.org is a reported attack page
by Rosanne DiMesio 13 Dec '13

13 Dec '13

A forum user reported that they got a "Reported Attack Page!" warning when they tried to download the Wine source tarball from mirrors.ibiblio.org. I checked, and I got the warning from Firefox, too. Chrome and Opera don't have a problem going to the site from the link here, but googling ibiblio.org brings up a warning that "This site may harm your computer" in all three browsers. -- Rosanne DiMesio <dimesio(a)earthlink.net>

1 0

Re: kernel32/tests: Remove some expected values for test_DeleteFileA()
by Dmitry Timoshkov 12 Dec '13

12 Dec '13

Zhenbo Li <litimetal(a)gmail.com> wrote: > There're too many expected values from GetLastError(), and I think it > might be confusing. Usually there was a reason why there are so many different results in ok() statements, it would be a good idea to check git history and find out that reasons it out instead of simply declaring them as confusing and removing them altogether. -- Dmitry.

2 1

Re: [3/4] secur32/tests: Add a test for QueryCredentialsAttributes(SECPKG_CRED_ATTR_NAMES). Take 2.
by Nikolay Sivov 12 Dec '13

12 Dec '13

On 12/12/2013 09:13, Dmitry Timoshkov wrote: > + > + st = pQueryCredentialsAttributesA(&cred, SECPKG_CRED_ATTR_NAMES, &names); > + ok(st == SEC_E_NO_CREDENTIALS || st == SEC_E_UNSUPPORTED_FUNCTION /* before Vista */, "expected SEC_E_NO_CREDENTIALS, got %08x\n", st); > + Second possible return code should be broken(), otherwise your code change in next patch won't make any effect on tests.

2 5

Re: [PATCH 3/6] d3d9/tests: Test user memory and getdc interaction.
by Henri Verbeet 11 Dec '13

11 Dec '13

On 11 December 2013 12:22, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > + data = HeapAlloc(GetProcessHeap(), 0, sizeof(data) * 16 * 16); > + memset(data, 0xaa, sizeof(data) * 16 * 16); I think you meant "sizeof(*data)" here.

2 1

Re: [2/2] programs/msiexec: MSI service should report SERVICE_STOPPED when appropriate.
by André Hentschel 11 Dec '13

11 Dec '13

Am 11.12.2013 09:16, schrieb Dmitry Timoshkov: > --- > programs/msiexec/service.c | 9 ++++++++- > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/programs/msiexec/service.c b/programs/msiexec/service.c > index 4b72fe0..fdd29bd 100644 > --- a/programs/msiexec/service.c > +++ b/programs/msiexec/service.c > @@ -81,6 +81,8 @@ static BOOL UpdateSCMStatus(DWORD dwCurrentState, DWORD dwWin32ExitCode, > > static void WINAPI ServiceCtrlHandler(DWORD code) > { > + DWORD state = SERVICE_RUNNING; > + > WINE_TRACE("%d\n", code); > > switch (code) > @@ -89,13 +91,14 @@ static void WINAPI ServiceCtrlHandler(DWORD code) > case SERVICE_CONTROL_STOP: > UpdateSCMStatus(SERVICE_STOP_PENDING, NO_ERROR, 0); > KillService(); > + state = SERVICE_STOPPED; > return; Hi, setting the variable here seems to have no effect i just have seen that from the patch without a look at the code, so i still might be wrong...

1 0

Bugzilla emails in html format after update
by Bruno Jesus 11 Dec '13

11 Dec '13

Hi, after the bugzilla update today I started receiving all emais in html format even with the preferences set to text email (double checked). For some reason gmail/firefox uses very small fonts to display the bug comments in this new format and it's quite unreadable for me. Is anyone else receiving html emails even with text emails configured in preferences? Or is there any other preference that need to be changed in order to have the text emails back? Best wishes, Bruno

3 3

Re: [PATCH 2/5] wined3d: Recreate DIB sections in wined3d_surface_update_desc().
by Stefan Dösinger 11 Dec '13

11 Dec '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 2013-12-11 14:32, schrieb Henri Verbeet: > Since commit 6bc69c271bf440b4ecad012dc57888fdffc075d5, the GDI > implementation assumes DIB sections always exist. Actually the idea behind this patch was that all paths that need a DIB section create one if necessary. Is there a place where that's not true? If it's about x11_copy_to_screen I think the better fix is calling surface_getdc from there. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSqHuLAAoJEN0/YqbEcdMwreEP/RCg6dr20bqTzc+P3HB+mvIO JCURzQz25PzWTnIn4+M3f8a/NcHP0Fu6621Te71Y2kk+be1ncIDMI9SAEAOzP4cW ELwmSlxgDUgZIx8w+cR8ce56Jg+ESesNEfPqwT7oWSVHnJqZnouo8IBp8xXCHc3K J+ACLw8PWZoorXg9YVVLrVWwEyxr1mamQE/35WlXEMRJ/6gqZwdML6bCY/wVJ/Vf 18lBebBy9aluiXKyuEUQA1rz1n4Ji7Cz6IFiK+TGGkiPk9WHJekG3tREI9LoT4Hi VFrktfl/3P1wNb4/ab2U0xjbVOPdtqHqSU6RWfB+jjI3VvzLjjtinI/5I5ip2f8u f7XFm8EV2+0czBjXwgaIouWYYEKIEE1wZKZBPjUU+RQUKfdohuSD/QCNC9E3uf7f qhR01J3M4O6z41RJGwBMBwI2lHsEQWZaj3rsryJzo2mxRoMvv/ksV7oB75mgPQaz jShTnEvs4SMFh9PMkANNpRVUWvVu0b27hUeIvlo2GbNDhJKsnll0YFQfL6eKm29y Kr7ltkqRoWyeA/2Q3IGBTFF0l1a1F9JAgZxy8SRqpykglfc0ekCazGhQUku0Vi1/ 1lvnzf2K9RkT5gIPlMmxuHTmEunc4wdk2T7SsEZK8htnMTqIyV+XoaSyjezg1K2R uDCAYLqI+6lx9j5r31xR =tLfE -----END PGP SIGNATURE-----

2 2

Re: [5/5] ws2_32: Move the buffer used by inet_ntoa into the per thread data.
by Marvin 11 Dec '13

11 Dec '13

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=3722 Your paranoid android. === wxppro (32 bit sock) === sock.c:520: Test failed: oob_server (4c0): unexpectedly at the OOB mark: 0 sock: unhandled exception c0000005 at 00000000 === w2008s64 (32 bit sock) === sock.c:520: Test failed: oob_server (750): unexpectedly at the OOB mark: 0

1 0

Re: [4/5] ws2_32/tests: Add a test for inet_ntoa called from two threads.
by Marvin 11 Dec '13

11 Dec '13

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=3721 Your paranoid android. === wxppro (32 bit sock) === sock.c:520: Test failed: oob_server (c0): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:520: Test failed: oob_server (750): unexpectedly at the OOB mark: 0 === w2008s64 (64 bit sock) === sock.c:520: Test failed: oob_server (654): unexpectedly at the OOB mark: 0 sock: unhandled exception c0000005 at 000007FEFE4C9CD9

1 0

Re: [4/4] secur32: Make schannel implementation of QueryCredentialsAttributes(SECPKG_CRED_ATTR_NAMES) return SEC_E_NO_CREDEN
by Marvin 11 Dec '13

11 Dec '13

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=3720 Your paranoid android. === wxppro (32 bit schannel) === schannel.c:305: Test failed: expected SEC_E_NO_CREDENTIALS, got 80090302 schannel.c:800: Test failed: expected SEC_E_NO_CREDENTIALS, got 80090302

1 0

Re: [3/4] secur32/tests: Add a test for QueryCredentialsAttributes(SECPKG_CRED_ATTR_NAMES).
by Marvin 11 Dec '13

11 Dec '13

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=3719 Your paranoid android. === wxppro (32 bit schannel) === schannel.c:306: Test failed: expected SEC_E_NO_CREDENTIALS, got 80090302 schannel.c:802: Test failed: expected SEC_E_NO_CREDENTIALS, got 80090302

1 0

Re: [PATCH 5/5] d3d9: shared_handle must be NULL in non-ex d3d9 (try 2).
by Marvin 11 Dec '13

11 Dec '13

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=3709 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 4/5] d3d9: Implement user memory for offscreen plain surfaces (try 4).
by Marvin 11 Dec '13

11 Dec '13

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=3708 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 3/5] d3d9: Buffers do not support user memory (try 4).
by Marvin 11 Dec '13

11 Dec '13

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=3707 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 2/5] d3d9: Volume and cube textures do not support user memory (try 4).
by Marvin 11 Dec '13

11 Dec '13

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=3706 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 1/5] d3d9/tests: Test user memory with D3DPOOL_SCRATCH (try 3).
by Marvin 11 Dec '13

11 Dec '13

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=3705 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 5/5] d3d9: shared_handle must be NULL in non-ex d3d9.
by Marvin 11 Dec '13

11 Dec '13

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=3704 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 4/5] d3d9: Implement user memory for offscreen plain surfaces (try 3).
by Marvin 11 Dec '13

11 Dec '13

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=3703 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 3/5] d3d9: Buffers do not support user memory (try 3).
by Marvin 11 Dec '13

11 Dec '13

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=3702 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 2/5] d3d9: Volume and cube textures do not support user memory (try 3).
by Marvin 10 Dec '13

10 Dec '13

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=3701 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [1/2] gdi32: Return ANSI character code as glyph index for bitmap fonts.
by Alexandre Julliard 10 Dec '13

10 Dec '13

Akihiro Sagawa <sagawa.aki(a)gmail.com> writes: > @@ -5975,7 +5975,7 @@ static FT_UInt get_GSUB_vert_glyph(const GdiFont *font, UINT glyph) > return GSUB_apply_feature(header, feature, glyph); > } > > -static FT_UInt get_glyph_index(const GdiFont *font, UINT glyph) > +static FT_UInt get_glyph_index(const GdiFont *font, UINT glyph, BOOL ret_char_code) > { > FT_UInt glyphId; > It would be better to have a separate function instead of having the same function return two different types of index. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: include: Add taskschd.idl.
by Jacek Caban 10 Dec '13

10 Dec '13

Hi Dmitry, On 12/10/13 10:12, Dmitry Timoshkov wrote: > + HRESULT get_Connected([out, retval] VARIANT_BOOL *connected); > + HRESULT get_TargetServer([out, retval] BSTR *server); > + HRESULT get_ConnectedUser([out, retval] BSTR *user); > + HRESULT get_ConnectedDomain([out, retval] BSTR *domain); > + HRESULT get_HighestVersion([out, retval] DWORD *version); Those should use [propget] attribute instead of explicit get_* prefix. Same for other get_* and put_* methods (with [propput]). Cheers, Jacek

1 0

Re: [PATCH 1/5] d3d9/tests: Test user memory with D3DPOOL_SCRATCH (try 2).
by Henri Verbeet 10 Dec '13

10 Dec '13

On 10 December 2013 12:23, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > @Henri: I'm not sure what kind of control flow you had in mind here. The > best understanding I could come up with was a nested if (first check for > D3DPOOL_DEFAULT, then handle the D3DPOOL_SYSTEMEM special case), which I > think is ugly. I removed the case check for D3DPOOL_SCRATCH, at the cost > of not writing a visible FIXME for pool 0x6. ... > if (shared_handle) > { > - if (pool == D3DPOOL_SYSTEMMEM) > + switch (pool) > { > - if (levels != 1) > + case D3DPOOL_DEFAULT: > + FIXME("Resource sharing not implemented, *shared_handle %p.\n", *shared_handle); > + break; > + > + case D3DPOOL_SYSTEMMEM: > + if (levels != 1) > + { > + WARN("Trying to create a mipmapped user memory texture.\n"); > + return D3DERR_INVALIDCALL; > + } > + set_mem = TRUE; > + break; > + > + default: > + WARN("Trying to create a texture with pool %#x and shared_handle %p.\n", > + pool, shared_handle); > return D3DERR_INVALIDCALL; > - set_mem = TRUE; > } > - else > - FIXME("Resource sharing not implemented, *shared_handle %p.\n", *shared_handle); > } > + { + if (pool != D3DPOOL_DEFAULT) + { + WARN("Trying to create a shared texture in pool %#x.\n", pool); + return D3DERR_INVALIDCALL; + } FIXME("Resource sharing not implemented, *shared_handle %p.\n", *shared_handle); + }

1 0

Re: [PATCH 1/5] d3d9/tests: Test user memory with D3DPOOL_SCRATCH (try 2).
by Marvin 10 Dec '13

10 Dec '13

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=3700 Your paranoid android. === build (build) === Could not copy the patch to the VM: Unable to connect to testnet.winehq.org:22001:10.42.42.130:4242: No route to host

1 0

Implementing msvcrt.__CxxFrameHandler
by Alexandre Bique 09 Dec '13

09 Dec '13

Hi, I found that __CxxFrameHandler is not implemented for wine64, and I'd like to fix this because I think it is the reason why Ableton Live 9.1 is crashing at start up. If someone can implement it, then it is great! Otherwise if someone can give me guidelines, I can try to understand how it works and do it myself. Here is a previous email talking about this: http://www.winehq.org/pipermail/wine-devel/2011-April/089617.html Here is the bug about Ableton Live 9.1: http://bugs.winehq.org/show_bug.cgi?id=35092 Regards, -- Alexandre Bique

1 0

Re: [PATCH 1/4] d3d9/tests: Test user memory with D3DPOOL_SCRATCH.
by Henri Verbeet 09 Dec '13

09 Dec '13

On 9 December 2013 13:28, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > The undocumented d3d9ex managed pool with enum value 6 does not allow > user memory textures either. I'm not including tests for that yet > until our d3d9 can handle this pool. I'm not quite sure I see the point of this test. The way the docs say this works is that in the general case resource sharing only works with default pool resources. Creating system memory textures with user memory backing is an exception to that. So I'd expect this test to fail in the first place because the resource is not in the default pool, and in the second place because the handle you're passing is most likely not a valid resource handle.

1 0

Re: [PATCH 2/4] d3d9: Volume and cube textures do not support user memory (try 2).
by Henri Verbeet 09 Dec '13

09 Dec '13

On 9 December 2013 13:28, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > if (shared_handle) > + { > + if (pool != D3DPOOL_DEFAULT) > + { > + WARN("User memory is not allowed on volume textures.\n"); Similarly, I don't think this warning really represent what's going on. The issue is that resource sharing is only allowed with default pool resources. (And quite possibly only on d3d9ex devices.)

1 0

Mobile version input methods (on-screen buttons, keyboards, virtual joysticks)
by WineBuG 08 Dec '13

08 Dec '13

How would you deal with lack of the keyboard and mouse in the future ARM (Android) version of Wine? Will one be able to add virtual on-screen buttons and joysticks in some way? Are you going to analyze controls solutions of other mobile apps (for example, games)? Regards, WineBuG

1 0

Build issues with winemac.drv and Mavericks
by C.W. Betts 08 Dec '13

08 Dec '13

I’ve run into issues when building winemac.drv on Mavericks. Attached is the log.

3 3

Mobile version input methods (on-screen buttons, keyboards, virtual joysticks)
by WineBuG 07 Dec '13

07 Dec '13

How would cope with lack of the keyboard and mouse in the future ARM (Android) version of Wine? Will one be able to add virtual on-screen buttons and joysticks in some way? Are you going to analyze other mobile apps (for example, games) controls solutions? Regards, WineBuG

1 0

Re: [PATCH] user32: Don't send message to get window text, avoid a deadlock.
by Dmitry Timoshkov 07 Dec '13

07 Dec '13

Qian Hong <qhong(a)codeweavers.com> wrote: > - Fixed http://bugs.winehq.org/show_bug.cgi?id=27282, affects Arcania: > Gothic 4 and online bank of abchina and > - Makes Anastasius happy :p This patch needs at least some tests. -- Dmitry.

2 1

Re: [PATCH 2/5] ole32: Simplify enumeration cloning using duplicated key
by Alexandre Julliard 06 Dec '13

06 Dec '13

Nikolay Sivov <nsivov(a)codeweavers.com> writes: > - new_this->IEnumCATEGORYINFO_iface = This->IEnumCATEGORYINFO_iface; > - new_this->ref = 1; > - new_this->lcid = This->lcid; > - /* FIXME: could we more efficiently use DuplicateHandle? */ > - open_classes_key(HKEY_CLASSES_ROOT, keyname, KEY_READ, &new_this->key); > - new_this->next_index = This->next_index; > + cloned->IEnumCATEGORYINFO_iface = This->IEnumCATEGORYINFO_iface; > + cloned->ref = 1; > + cloned->lcid = This->lcid; > > - *ppenum = &new_this->IEnumCATEGORYINFO_iface; > + if (!DuplicateHandle(GetCurrentProcess(), This->key, GetCurrentProcess(), (HANDLE*)&cloned->key, 0, FALSE, DUPLICATE_SAME_ACCESS)) > + { > + IEnumCATEGORYINFO_Release(&cloned->IEnumCATEGORYINFO_iface); > + return E_FAIL; > + } Using DuplicateHandle is not a good idea on registry keys, particularly for HKEY_CLASSES_ROOT keys. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: shell32/tests: Use GetVersion() to skip Timeout test (try 2)
by Nikolay Sivov 06 Dec '13

06 Dec '13

On 12/6/2013 09:10, Zhenbo Li wrote: > I'm using win_skip() for Vista&Win2008 this time. > > --- > dlls/shell32/tests/shlfileop.c | 36 +++++++++++++++++++----------------- > 1 file changed, 19 insertions(+), 17 deletions(-) > > Hm, it's the same issue. Please don't use GetVersion().

1 0

Re: shell32/tests: Use GetVersion() to skip Timeout test (try 2)
by Marvin 06 Dec '13

06 Dec '13

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=3671 Your paranoid android. === wvista (32 bit shlfileop) === Timeout === w2008s64 (32 bit shlfileop) === Timeout === w2008s64 (64 bit shlfileop) === Timeout

1 0

Re: wined3d: Use BOOL type where appropriate
by Henri Verbeet 06 Dec '13

06 Dec '13

On 5 December 2013 23:14, Frédéric Delanoy <frederic.delanoy(a)gmail.com> wrote: > Note: in surface.c, used "?1:0" construct to avoid implicit BOOL arithmetic > --- > dlls/wined3d/arb_program_shader.c | 19 +++++++++---------- > dlls/wined3d/context.c | 20 ++++++++++---------- > dlls/wined3d/device.c | 2 +- > dlls/wined3d/gl_compat.c | 4 ++-- > dlls/wined3d/shader.c | 20 ++++++++++---------- > dlls/wined3d/stateblock.c | 22 +++++++++++----------- > dlls/wined3d/surface.c | 8 ++++---- > dlls/wined3d/utils.c | 8 ++++---- > 8 files changed, 51 insertions(+), 52 deletions(-) > I don't think so, most of these are bitfields, and the surface.c change is actually making the code worse.

1 0

Re: [PATCH 3/3] ws2_32: Add an interactive test for interface change notifications (resend 2).
by Marvin 05 Dec '13

05 Dec '13

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=3670 Your paranoid android. === wxppro (32 bit sock) === sock.c:520: Test failed: oob_server (4c0): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:520: Test failed: oob_server (750): unexpectedly at the OOB mark: 0 sock: unhandled exception c0000005 at 757C9799 === w2008s64 (64 bit sock) === sock.c:520: Test failed: oob_server (744): unexpectedly at the OOB mark: 0 No test summary line found === w864 (64 bit sock) === sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1748: Test failed: getservbyname: winsock resized servent buffer when not necessary

1 0

Re: shell32/tests: Use GetVersion() to skip a test on Vista
by Zhenbo Li 05 Dec '13

05 Dec '13

2013/12/5 Nikolay Sivov <bunglehead(a)gmail.com>: > Ok, I'll try. > > It's discouraged to check system version in wine tests that's what I'm > saying. One of the reason for that is > that we don't want to skip anything running tests on wine, no matter what > windows version is selected for a prefix. > Proper win_skip() should check for broken or unwanted behaviour directly, by > calling affected APIs. That's what existing code does. Thank you, I think I got your meaning, but I don't think the old solution is a proper way. The patch were admitted in Jan 2009[1], when Vista was the latest win version. So such code + if (ret != ERROR_FILE_NOT_FOUND) can differ XP and Vista (XP would return 0x402, unknown error) But as MSDN [2] says, "This error does not occur on Windows Vista and later." So such code would skip all the windows versions except WinXP (I've confirmed it with TestBots) And now comes the problem. If I call SHFileOperation, XP returns 0x402, Win 7/8 returns ERROR_FILE_NOT_FOUND And in Vista / WIn2008, the testjob would be timeout (As Paul Vriens had mentioned, a dialog would appear) I can't see a better way to solve this problem now. Or could I use strcmp(winetest_platform, "windows") ? [1] :commit 30bb78f0f9c3441201f3aa31ebaf93f46b7c28ea Author: Paul Vriens <Paul.Vriens.Wine(a)gmail.com> Date: Fri Jan 9 07:46:11 2009 +0100 shell32/tests: Skip a test on Vista. [2]: http://msdn.microsoft.com/en-us/library/windows/desktop/bb762164%28v=vs.85%… -- Have a nice day! Zhenbo Li

1 0

Re: ddraw/tests: Fix compilation on systems that don't support nameless unions.
by Marvin 05 Dec '13

05 Dec '13

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=3665 Your paranoid android. === w8 (32 bit ddraw4) === ddraw4.c:3323: Test failed: SetDisplayMode failed, hr 0x80004001. === w864 (32 bit ddraw4) === ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x8, expected 0x80070057.

1 0

Re: [PATCH 5/5] ddraw: Properly flip through the swap chain in ddraw_surface7_Flip().
by Marvin 05 Dec '13

05 Dec '13

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=3663 Your paranoid android. === w864 (64 bit ddraw7) === The test timed out === w8 (32 bit ddraw4) === ddraw4.c:3323: Test failed: SetDisplayMode failed, hr 0x80004001. === w864 (32 bit ddraw4) === ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x8, expected 0x80070057.

1 0

Re: ws2_32: Avoid writing to NULL pointer (coverity)
by Alexandre Julliard 05 Dec '13

05 Dec '13

Bruno Jesus <00cpxxx(a)gmail.com> writes: > Due to the format set in sprintf this is impossible to happen, but > coverity is not content aware and complains that the strstr may return > NULL. This patch should make it happy. If it can't happen there's no reason to add a check. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: [PATCH 3/5] ddraw/tests: Add a test for primary surface capabilities.
by Marvin 05 Dec '13

05 Dec '13

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=3662 Your paranoid android. === w8 (32 bit ddraw2) === ddraw2.c:3091: Test failed: SetDisplayMode failed, hr 0x80004001. === w864 (32 bit ddraw2) === Failure running script in VM: network read timed out === w8 (32 bit ddraw4) === ddraw4.c:3323: Test failed: SetDisplayMode failed, hr 0x80004001. === w864 (32 bit ddraw4) === ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x8, expected 0x80070057.

1 0

Re: shell32/tests: Use GetVersion() to skip a test on Vista
by Nikolay Sivov 05 Dec '13

05 Dec '13

On 12/5/2013 13:48, Zhenbo Li wrote: > There are few lines in the code: > > + if (ret != ERROR_FILE_NOT_FOUND) > + { > + /* Vista would throw up a dialog box that we can't suppress */ > > As this problem only exists in Vista && Windows 2008, so I think use > GetVersion() is a better idea. > > --- > dlls/shell32/tests/shlfileop.c | 13 ++++++++----- > 1 file changed, 8 insertions(+), 5 deletions(-) > > It's better as it is, just add a comment about win2008 if you like. The rule is to skip basing on functionality instead of simple version check.

1 0

Re: [1/2] wineconsole: Calculate the maximum possible console window size
by Vincent Povirk 05 Dec '13

05 Dec '13

+ c.X = (workarea.right / cell_width) - 4; + c.Y = (workarea.bottom / cell_height) - 3; I think you probably want the size of the workarea (right-left, bottom-top), not the position of the workarea's lower-right corner.

2 1

Re: [PATCH 4/4] d3d9: Implement user memory for offscreen plain surfaces.
by Marvin 05 Dec '13

05 Dec '13

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=3653 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 3/4] d3d9: Buffers do not support user memory.
by Marvin 05 Dec '13

05 Dec '13

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=3652 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 2/4] d3d9: Volume and cube textures do not support user memory.
by Marvin 05 Dec '13

05 Dec '13

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=3651 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 1/4] d3d9/tests: Extend the sysmem texture mipmap test.
by Marvin 05 Dec '13

05 Dec '13

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=3650 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 3/5] ddraw: Validate that surfaces are on the same swap chain in ddraw_surface7_Flip().
by Marvin 05 Dec '13

05 Dec '13

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=3648 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 2/5] ddraw: Attach the first surface in the swap chain to the last one.
by Marvin 05 Dec '13

05 Dec '13

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=3647 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 1/5] ddraw: Reject flips of surfaces with themselves.
by Marvin 05 Dec '13

05 Dec '13

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=3646 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 3/3] comctl32/tests: Finally compile with -D__WINESRC__.
by Marvin 05 Dec '13

05 Dec '13

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=3645 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 2/3] comctl32/tests: Make treeview.c compile with -D__WINESRC__.
by Marvin 05 Dec '13

05 Dec '13

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=3644 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 1/3] comctl32/tests: Avoid non-AW aware TreeView_*() macros.
by Marvin 05 Dec '13

05 Dec '13

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=3643 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3638 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3637 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3636 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3635 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3634 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3633 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3632 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3631 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 3/5] ddraw: Only set DDSCAPS_VISIBLE on the root surface.
by Marvin 05 Dec '13

05 Dec '13

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=3618 Your paranoid android. === w864 (32 bit ddraw7) === No test summary line found Failure running script in VM: network read timed out === w864 (32 bit ddraw4) === ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x8, expected 0x80070057. Failure running script in VM: timed out waiting for the child process

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3630 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3629 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3628 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: Assorted spelling fixes
by Marvin 05 Dec '13

05 Dec '13

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=3627 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 5/5] ddraw/tests: Test SetSurfaceDesc and Lock interaction.
by Marvin 05 Dec '13

05 Dec '13

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=3625 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 4/5] ddraw: Check for lpSurface=NULL in SetSurfaceDesc.
by Marvin 04 Dec '13

04 Dec '13

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=3624 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 3/5] ddraw: SetSurfaceDesc accepts DDSD_CAPS with dwCaps=0.
by Marvin 04 Dec '13

04 Dec '13

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=3623 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 2/5] ddraw: SetSurfaceDesc is not allowed on managed textures.
by Marvin 04 Dec '13

04 Dec '13

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=3622 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 1/5] ddraw/tests: Add a surface flipping test.
by Marvin 04 Dec '13

04 Dec '13

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=3617 Your paranoid android. === w8 (32 bit ddraw2) === ddraw2.c:3091: Test failed: SetDisplayMode failed, hr 0x80004001. === w864 (32 bit ddraw7) === The test timed out === w864 (32 bit ddraw4) === ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 1x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 2x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 3x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 4x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 5x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 6x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 7x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x1, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x8, expected 0x80070057.

1 0

Re: [PATCH 1/5] ddraw/tests: Port test_set_surface_desc to other versions.
by Marvin 04 Dec '13

04 Dec '13

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=3621 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 5/5] ddraw: Return the correct error in ddraw_surface7_Flip() when the surface is not flippable.
by Marvin 04 Dec '13

04 Dec '13

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=3620 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 4/5] ddraw: Only set DDSCAPS_FRONTBUFFER on flippable surfaces.
by Marvin 04 Dec '13

04 Dec '13

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=3619 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 3/5] wined3d: Temporarily remove surface PBO support.
by Henri Verbeet 04 Dec '13

04 Dec '13

On 24 November 2013 00:18, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > The implementation is strange and fairly ineffective in doing what PBOs > are supposed to do - avoiding pipeline stalls and redundant copying. > Removing it will make restructuring surfaces easier and avoid temporary > regressions. It will be re-added later. Is there a good reason this can't just be fixed first?

2 7

Re: [PATCH 2/4] d3d9: Volume and cube textures do not support user memory.
by Henri Verbeet 04 Dec '13

04 Dec '13

On 4 December 2013 14:01, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > + if (pool == D3DPOOL_SYSTEMMEM) > + { > + WARN("User memory is not allowed on volume textures.\n"); > + return D3DERR_INVALIDCALL; > + } > + else > + FIXME("Resource sharing not implemented, *shared_handle %p.\n", *shared_handle); > + } > The docs suggest the check should be "pool != D3DPOOL_DEFAULT". You can also drop the else-branch because you return.

1 0

Re: [PATCH 2/3] server: Implement an interface change notification object (rebased).
by Alexandre Julliard 04 Dec '13

04 Dec '13

"Erich E. Hoover" <erich.e.hoover(a)gmail.com> writes: > +static void ifchange_poll_event( struct fd *fd, int event ) > +{ > + struct object *ifchange = get_fd_user( fd ); > + int r, unix_fd, wakeup = FALSE; > + char buffer[0x1000]; > + > + unix_fd = get_unix_fd( fd ); > + r = recv( unix_fd, buffer, sizeof(buffer), 0 ); > + if (r < 0) > + { > + fprintf(stderr,"ifchange_poll_event(): ifchange read failed!\n"); > + return; > + } > + else if (r != 0) > + { > +#if defined(NETLINK_ROUTE) > + struct nlmsghdr *nlh; > + > + nlh = (struct nlmsghdr*) buffer; > + if (NLMSG_OK(nlh, r) && (nlh->nlmsg_type == RTM_NEWADDR || nlh->nlmsg_type == RTM_DELADDR)) > + wakeup = TRUE; > +#endif > + } > + if (wakeup) > + ifchange_wake_up( ifchange, STATUS_SUCCESS ); > +} This needs more work. Also please try to better follow wineserver conventions everywhere. -- Alexandre Julliard julliard(a)winehq.org

1 0

RE: programs/xcopy: fix a typo in a comment
by Hugh McMaster 03 Dec '13

03 Dec '13

On Saturday, 30 November 2013 4:28 pm, Austin English wrote: > /* Microsoft's xcopy's usage implies that the date >- * format depends on the locale but that false. >+ * format depends on the locale but that is false. > * It is hardcoded to month-day-year > */ Hi Austin, It would be a good idea to fix the first line of the comment as well. Something like: "Usage of Microsoft's xcopy implies that the date" Hugh

3 2

FOSDEM '14 Call for Papers
by Jeremy White 02 Dec '13

02 Dec '13

Folks, There will a Wine devroom at FOSDEM '14 on Sunday, February 2, 2014. Last year we had a great time, and I think it was valuable for us to connect with the broader Free software community. I'd like to now invite you to submit proposals for talks. I'd really like to encourage everyone to think of something fun to share with the 5,000 geeks that will be swarming Brussels. If you have an topic you'd like to discuss, or an idea you want to present, please submit it to: https://penta.fosdem.org/submission You will create an account (if you don't have one from a previous year), and select the "Wine devroom" as the track. Please either submit for lengths of 30 or 60 minutes. The deadline for submissions is December 1st. I think it would be great if we branched out a bit, and submitting a crazy off the wall proposal will just burn churn a few electrons. So submit it! For further discussion, please follow up to wineconf(a)winehq.org. Cheers, Jeremy

1 1

Re: [PATCH 5/5] ddraw/tests: Unify the skip messages a bit.
by Marvin 02 Dec '13

02 Dec '13

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=3603 Your paranoid android. === w864 (32 bit ddraw4) === ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x2, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x3, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x4, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x5, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x6, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x7, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x8, expected 0. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x8, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x1, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x2, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x3, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x4, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x5, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x6, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x7, expected 0x80070057. ddraw4.c:4105: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x8, expected 0x80070057.

1 0

Re: [PATCH 4/5] ddraw/tests: Add some missing DestroyWindow() calls.
by Marvin 02 Dec '13

02 Dec '13

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=3602 Your paranoid android. === w864 (32 bit ddraw4) === ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x2, expected 0. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x3, expected 0. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x4, expected 0. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x5, expected 0. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x6, expected 0. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x7, expected 0. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_YUY2, resource type videomemory overlay, size 8x8, expected 0. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x1, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x2, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x3, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x4, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x5, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x6, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x7, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 1x8, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x1, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x2, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x3, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x4, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x5, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x6, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x7, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 2x8, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x1, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x2, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x3, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x4, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x5, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x6, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x7, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 3x8, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x1, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x2, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x3, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x4, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x5, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x6, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x7, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 4x8, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x1, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x2, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x3, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x4, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x5, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x6, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x7, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 5x8, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x1, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x2, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x3, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x4, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x5, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x6, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x7, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 6x8, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x1, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x2, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x3, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x4, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x5, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x6, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x7, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 7x8, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x1, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x2, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x3, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x4, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x5, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x6, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x7, expected 0x80070057. ddraw4.c:4106: Test failed: Got unexpected hr 0x88760104 for format D3DFMT_UYVY, resource type videomemory overlay, size 8x8, expected 0x80070057.

1 0

Re: winex11.drv: Remove spaces in WARN and TRACE messages.
by Henri Verbeet 02 Dec '13

02 Dec '13

On 1 December 2013 19:18, Andrey Gusev <andrey.goosev(a)gmail.com> wrote: > - WARN( "X Input 2 not available\n" ); > + WARN( "XInput2 not available\n" ); The extension is actually called the "X Input Extension", so I think the existing messages are more correct.

1 0

Re: comctl32/tests: Better deal with the unsupported CreateWindowExW() case.
by Nikolay Sivov 02 Dec '13

02 Dec '13

On 12/1/2013 19:24, Francois Gouget wrote: > No matter why CreateWindowExW() fails, if we don't have an hwnd we have > to skip the tests. > --- > It doesn't look like we have to use *Ex version at all.

2 1

Re: mshtml: Avoid memory leaks (coverity)
by Jacek Caban 30 Nov '13

30 Nov '13

Hi Frédéric, On 11/30/13 15:16, Frédéric Delanoy wrote: > CID 1131417 > --- > dlls/mshtml/htmlbody.c | 12 +++++++++--- > 1 file changed, 9 insertions(+), 3 deletions(-) > > diff --git a/dlls/mshtml/htmlbody.c b/dlls/mshtml/htmlbody.c > index fcd8766..163f0ba 100644 > --- a/dlls/mshtml/htmlbody.c > +++ b/dlls/mshtml/htmlbody.c > @@ -648,7 +648,8 @@ static HRESULT WINAPI HTMLBodyElement_get_scroll(IHTMLBodyElement *iface, BSTR * > > if(!overflow || !*overflow) { > *p = NULL; > - return S_OK; > + hres = S_OK; > + goto cleanup; > }else if(!strcmpW(overflow, visibleW) || !strcmpW(overflow, autoW)) { > ret = autoW; > }else if(!strcmpW(overflow, scrollW)) { > @@ -658,11 +659,16 @@ static HRESULT WINAPI HTMLBodyElement_get_scroll(IHTMLBodyElement *iface, BSTR * > }else { > TRACE("Defaulting %s to NULL\n", debugstr_w(overflow)); > *p = NULL; > - return S_OK; > + hres = S_OK; > + goto cleanup; > } > > *p = SysAllocString(ret); > - return *p ? S_OK : E_OUTOFMEMORY; > + hres = *p ? S_OK : E_OUTOFMEMORY; > + > +cleanup: > + SysFreeString(overflow); > + return hres; > } > Good catch, but those gotos make the code more complicated that it needs to be. You may just remove early returns and free overflow before allocating the result. Jacek

1 0

Re: qmgr/tests: Skip tests on Windows instead of failing
by Nikolay Sivov 29 Nov '13

29 Nov '13

On 11/29/2013 23:12, André Hentschel wrote: > Some w2k and win7 machines... > --- > dlls/qmgr/tests/enum_files.c | 2 +- > dlls/qmgr/tests/file.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/dlls/qmgr/tests/enum_files.c b/dlls/qmgr/tests/enum_files.c > index 7e2ab1e..a77f1e7 100644 > --- a/dlls/qmgr/tests/enum_files.c > +++ b/dlls/qmgr/tests/enum_files.c > @@ -256,7 +256,7 @@ START_TEST(enum_files) > /* Keep state separate between tests. */ > if (!setup()) > { > - ok(0, "tests:%d: Unable to setup test\n", i); > + win_skip("tests:%d: Unable to setup test, skipping tests\n", i); > break; > } I guess it's just fails to create an manager instance, please add a copy of test_create_manager() for that. > +++ b/dlls/qmgr/tests/file.c > @@ -197,7 +197,7 @@ START_TEST(file) > /* Keep state separate between tests. */ > if (!setup()) > { > - ok(0, "tests:%d: Unable to setup test\n", i); > + win_skip("tests:%d: Unable to setup test, skipping tests\n", i); > break; > } > (*test)(); This one is different as file.c already skips everything if initial object creation fails. We need to know where setup() fails exactly.

1 0

Re: [PATCH 2/3] wined3d: Pass a struct wined3d_bo_address to read_from_framebuffer.
by Henri Verbeet 28 Nov '13

28 Nov '13

On 28 November 2013 10:48, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > /* Read the framebuffer back into the surface */ > -static void read_from_framebuffer(struct wined3d_surface *surface, void *dest, UINT pitch) > +static void read_from_framebuffer(struct wined3d_surface *surface, > + const struct wined3d_bo_address *data, UINT pitch) It seems a bit silly to pass these as parameters when the only caller gets them from the surface.

2 2

Re: AUTHORS: Revert commit 5da31c8817293ff98b4defceb962f7d0fbc25829
by Austin English 28 Nov '13

28 Nov '13

On Nov 22, 2013 4:21 PM, "Tae Wong" <seotaewong40(a)gmail.com> wrote: > > You'll need to stop updating the AUTHORS list automatically. Why? > It's the command that GIT uses: > git revert 5da31c8817293ff98b4defceb962f7d0fbc25829 > > If you revert the commit, you'll be able to update it manually. There's no good reason to do this manually when git can do it automatically. If you see a problem with sorting, file a bug upstream with git. The lack of replies to this topic (that you've repeatedly sent, on different threads) should indicate that the patch was intentional and won't reverted. Cheers, Austin

3 3

Re: [PATCH 2/3] wined3d: Pass a struct wined3d_bo_address to read_from_framebuffer.
by Henri Verbeet 28 Nov '13

28 Nov '13

On 28 November 2013 10:48, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > --- > dlls/wined3d/surface.c | 54 +++++++++++++++++++++----------------------------- > 1 file changed, 23 insertions(+), 31 deletions(-) > > diff --git a/dlls/wined3d/surface.c b/dlls/wined3d/surface.c > index 744d6b9..e574956 100644 > --- a/dlls/wined3d/surface.c > +++ b/dlls/wined3d/surface.c > @@ -3438,7 +3438,8 @@ HRESULT CDECL wined3d_surface_flip(struct wined3d_surface *surface, struct wined > } > > /* Read the framebuffer back into the surface */ > -static void read_from_framebuffer(struct wined3d_surface *surface, void *dest, UINT pitch) > +static void read_from_framebuffer(struct wined3d_surface *surface, > + const struct wined3d_bo_address *data, UINT pitch) > { > struct wined3d_device *device = surface->resource.device; > const struct wined3d_gl_info *gl_info; > @@ -3489,7 +3490,7 @@ static void read_from_framebuffer(struct wined3d_surface *surface, void *dest, U > /* In case of P8 render targets the index is stored in the alpha component */ > fmt = GL_ALPHA; > type = GL_UNSIGNED_BYTE; > - mem = dest; > + mem = data->addr; > bpp = surface->resource.format->byte_count; > } > else > @@ -3518,21 +3519,18 @@ static void read_from_framebuffer(struct wined3d_surface *surface, void *dest, U > break; > > default: > - mem = dest; > + mem = data->addr; > fmt = surface->resource.format->glFormat; > type = surface->resource.format->glType; > bpp = surface->resource.format->byte_count; > } > > - if (surface->flags & SFLAG_PBO) > + if (data->buffer_object) > { > - GL_EXTCALL(glBindBufferARB(GL_PIXEL_PACK_BUFFER_ARB, surface->pbo)); > + GL_EXTCALL(glBindBufferARB(GL_PIXEL_PACK_BUFFER_ARB, data->buffer_object)); > checkGLcall("glBindBufferARB"); > if (mem) > - { > ERR("mem not null for pbo -- unexpected\n"); > - mem = NULL; > - } > } > > /* Save old pixel store pack state */ > @@ -3564,23 +3562,14 @@ static void read_from_framebuffer(struct wined3d_surface *surface, void *dest, U > gl_info->gl_ops.gl.p_glPixelStorei(GL_PACK_SKIP_ROWS, skipRow); > checkGLcall("glPixelStorei"); > > - if (surface->flags & SFLAG_PBO) > + if (data->buffer_object && !srcIsUpsideDown) > { > - GL_EXTCALL(glBindBufferARB(GL_PIXEL_PACK_BUFFER_ARB, 0)); > - checkGLcall("glBindBufferARB"); > - > /* Check if we need to flip the image. If we need to flip use glMapBufferARB > * to get a pointer to it and perform the flipping in software. This is a lot > * faster than calling glReadPixels for each line. In case we want more speed > * we should rerender it flipped in a FBO and read the data back from the FBO. */ > - if (!srcIsUpsideDown) > - { > - GL_EXTCALL(glBindBufferARB(GL_PIXEL_UNPACK_BUFFER_ARB, surface->pbo)); > - checkGLcall("glBindBufferARB"); > - > - mem = GL_EXTCALL(glMapBufferARB(GL_PIXEL_UNPACK_BUFFER_ARB, GL_READ_WRITE_ARB)); > - checkGLcall("glMapBufferARB"); > - } > + mem = GL_EXTCALL(glMapBufferARB(GL_PIXEL_PACK_BUFFER_ARB, GL_READ_WRITE_ARB)); > + checkGLcall("glMapBufferARB(GL_PIXEL_PACK_BUFFER_ARB, GL_READ_WRITE_ARB)"); > } > > /* TODO: Merge this with the palettization loop below for P8 targets */ > @@ -3611,15 +3600,19 @@ static void read_from_framebuffer(struct wined3d_surface *surface, void *dest, U > bottom -= pitch; > } > HeapFree(GetProcessHeap(), 0, row); > + } > > - /* Unmap the temp PBO buffer */ > - if (surface->flags & SFLAG_PBO) > - { > - GL_EXTCALL(glUnmapBufferARB(GL_PIXEL_UNPACK_BUFFER_ARB)); > - GL_EXTCALL(glBindBufferARB(GL_PIXEL_UNPACK_BUFFER_ARB, 0)); > - } > + if (data->buffer_object) > + { > + if (!srcIsUpsideDown) > + GL_EXTCALL(glUnmapBufferARB(GL_PIXEL_PACK_BUFFER_ARB)); > + > + GL_EXTCALL(glBindBufferARB(GL_PIXEL_PACK_BUFFER_ARB, 0)); > + checkGLcall("glBindBufferARB(GL_PIXEL_PACK_BUFFER_ARB, 0)"); > } > > + context_release(context); > + > /* For P8 textures we need to perform an inverse palette lookup. This is > * done by searching for a palette index which matches the RGB value. > * Note this isn't guaranteed to work when there are multiple entries for > @@ -3657,7 +3650,7 @@ static void read_from_framebuffer(struct wined3d_surface *surface, void *dest, U > && *green == pal[c].peGreen > && *blue == pal[c].peBlue) > { > - *((BYTE *) dest + y * width + x) = c; > + *((BYTE *)data->addr + y * width + x) = c; > break; > } > } > @@ -3665,8 +3658,6 @@ static void read_from_framebuffer(struct wined3d_surface *surface, void *dest, U > } > HeapFree(GetProcessHeap(), 0, mem); > } > - > - context_release(context); > } > > /* Read the framebuffer contents into a texture. Note that this function > @@ -5046,8 +5037,9 @@ static void surface_load_sysmem(struct wined3d_surface *surface, > > if (surface->flags & SFLAG_INDRAWABLE) > { > - read_from_framebuffer(surface, surface->resource.allocatedMemory, > - wined3d_surface_get_pitch(surface)); > + struct wined3d_bo_address data; > + surface_get_memory(surface, &data); > + read_from_framebuffer(surface, &data, wined3d_surface_get_pitch(surface)); > return; > } > > -- > 1.8.3.2 > > >

1 0

Re: [PATCH 3/6] wined3d: Move format conversion to surface_upload_data.
by Henri Verbeet 28 Nov '13

28 Nov '13

I'm not sure about this, why do we want this?

2 7

Wine Mono 4.5.2 Release
by Vincent Povirk 27 Nov '13

27 Nov '13

This is a small bugfix update because Andrew Eikum found a regression in upstream mono that I thought warranted it. As always, the msi can be installed in current Wine without any modification. Any testing before this gets into Wine would be appreciated. The source tarball is at https://sourceforge.net/projects/wine/files/Wine%20Mono/4.5.2/wine-mono-4.5… The binary is at https://sourceforge.net/projects/wine/files/Wine%20Mono/4.5.2/wine-mono-4.5… For developers, the source repository is at https://github.com/madewokherd/wine-mono Changes since 4.5.0: * Fixed CultureInfo.CurrentCultureInfo always returning InvariantCulture. (Andrew Eikum) * Fixed build on recent mingw versions that define __readfsdword. (Andrew Eikum) * Added the policy/v4.0 registry key to reflect support for .NET 4.

1 0

Re: winhttp/tests: Use BOOL type where appropriate
by Dmitry Timoshkov 27 Nov '13

27 Nov '13

Frédéric Delanoy <frederic.delanoy(a)gmail.com> wrote: > --- a/dlls/winhttp/tests/notification.c > +++ b/dlls/winhttp/tests/notification.c > @@ -44,9 +44,9 @@ struct notification > { > enum api function; /* api responsible for notification */ > unsigned int status; /* status received */ > - int todo; > - int ignore; > - int skipped_for_proxy; > + BOOL todo; > + BOOL ignore; > + BOOL skipped_for_proxy; Do you realize that BOOL is typedef'ed to int and therefore your patches do basically nothing? Is there any real reason behind these patches? -- Dmitry.

3 5

Re: Daemonizing wine (fix for issue #15462)
by Alexandre Julliard 27 Nov '13

27 Nov '13

Micha Nelissen <micha(a)neli.hopto.org> writes: > The patch creates a daemon.err logfile in the wine server dir > (/tmp/.wine-XXX/YYY/), where the output of wineserver.exe, > services.exe, and all other background processes go. I don't think that's a good idea. In the debugging case, you want all the traces to go to the same place, and when displaying errors, no user is ever going to see them in that file. Not to mention that the log file is going to grow endlessly. > I've removed the inheritance of stdin/stdout/stderr in > server/process.c (that took some time to find!) because in windows, > either you set bInheritHandles to true with CreateProcess and you > inherit stdin etc too, or you set it false, and you get nothing. So > this patch should also increase winapi compatibility. This should be a separate patch, with test cases. -- Alexandre Julliard julliard(a)winehq.org

2 4

Re: kernel32/tests: Add tests for job objects
by Marvin 27 Nov '13

27 Nov '13

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=3566 Your paranoid android. === w7pro64 (32 bit process) === process.c:2193: Test failed: Unexpected completion event: 7, 000001FC, 00000AB0 process.c:2210: Test failed: Unexpected completion event: 4, 000001FC, 00000000 process.c:2211: Test failed: Unexpected completion event: 6, 000001FC, 00000934 process.c:2212: Test failed: Unexpected completion event: 6, 000001FC, 00000AB8 process.c:2281: Test failed: Unexpected completion event: 7, 000001FC, 00000AB8 process.c:2309: Test failed: Unexpected completion event: 4, 0000023C, 00000000 process.c:2310: Test failed: Unexpected completion event: 6, 000001FC, 00000AE8 process.c:2311: Test failed: Unexpected completion event: 6, 000001FC, 00000AF0

1 0

Re: libport: Add a finite() portability macro and use it.
by Alexandre Julliard 26 Nov '13

26 Nov '13

Francois Gouget <fgouget(a)free.fr> writes: > --- > > This fixes compilation on Solaris machines. It should probably be a function along the lines of isinf and isnan. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: shell32: change return value of SHFileOperation when deleting files
by Nikolay Sivov 26 Nov '13

26 Nov '13

On 11/26/2013 19:37, Zhenbo Li wrote: > This patch should fix bug 34324. Does it actually fix it? Cause a hack attached to this bug differs from what you're doing. Another thing to test is to try this application on Vista or later to see if it works. > When deleting files, I can't find a situation to return > ERROR_PATH_NOT_FOUND > --- > dlls/shell32/shlfileop.c | 2 +- > dlls/shell32/tests/shlfileop.c | 3 --- > 2 files changed, 1 insertion(+), 4 deletions(-) >

3 3

Re: shell32: change return value of SHFileOperation when deleting files
by Qian Hong 26 Nov '13

26 Nov '13

Hi Zhenbo, thanks for the work. On Tue, Nov 26, 2013 at 11:37 PM, Zhenbo Li <litimetal(a)gmail.com> wrote: > When deleting files, I can't find a situation to return ERROR_PATH_NOT_FOUND Hmm, testing deleting an nonexistent path would be interesting too :) Try shfo.pFrom = "nonexistent\\nonexistent.txt\0"; and shfo.pFrom = "testdir2\0testdir2\0"; In these case, Windows may return ERROR_PATH_NOT_FOUND or ERROR_INVALID_LEVEL. -- Regards, Qian Hong - http://www.winehq.org

1 0

Re: [PATCH 4/4] wined3d: Don't store PBO pointers in allocatedMemory.
by Henri Verbeet 26 Nov '13

26 Nov '13

On 25 November 2013 23:41, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > @@ -817,6 +813,12 @@ static void surface_map(struct wined3d_surface *surface, const RECT *rect, DWORD > > context_release(context); > } > + else > + { > + ret = surface->resource.allocatedMemory; > + } > + > + return ret; > } > You don't really need an else-branch here, you can just return early in the PBO case.

1 0

Re: [PATCH 6/6] qcap: Fix Avi Mux output pin Connect implementation
by Marvin 26 Nov '13

26 Nov '13

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=3550 Your paranoid android. === w8 (32 bit qcap) === qcap.c:1293: Test failed: ReceiveConnection returned 80040200 qcap.c:1296: Test failed: ConnectedTo returned 80040209 qcap.c:1297: Test failed: incorrect pin: 00000000, expected 0023FC68 qcap.c:1315: Test failed: expected Reconnect === w864 (32 bit qcap) === qcap.c:1293: Test failed: ReceiveConnection returned 80040200 qcap.c:1296: Test failed: ConnectedTo returned 80040209 qcap.c:1297: Test failed: incorrect pin: 00000000, expected 0028FC58 qcap.c:1315: Test failed: expected Reconnect === w864 (64 bit qcap) === qcap.c:1293: Test failed: ReceiveConnection returned 80040200 qcap.c:1296: Test failed: ConnectedTo returned 80040209 qcap.c:1297: Test failed: incorrect pin: 0000000000000000, expected 000000000023FB30 qcap.c:1315: Test failed: expected Reconnect

1 0

Re: [PATCH 5/6] qcap: Add helper to initalize test_filter structure
by Marvin 26 Nov '13

26 Nov '13

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=3549 Your paranoid android. === w8 (32 bit qcap) === qcap.c:1162: Test failed: ReceiveConnection returned 80040200 qcap.c:1165: Test failed: ConnectedTo returned 80040209 qcap.c:1166: Test failed: incorrect pin: 00000000, expected 0023FD64 === w864 (32 bit qcap) === qcap.c:1162: Test failed: ReceiveConnection returned 80040200 qcap.c:1165: Test failed: ConnectedTo returned 80040209 qcap.c:1166: Test failed: incorrect pin: 00000000, expected 0028FD54 === w864 (64 bit qcap) === qcap.c:1162: Test failed: ReceiveConnection returned 80040200 qcap.c:1165: Test failed: ConnectedTo returned 80040209 qcap.c:1166: Test failed: incorrect pin: 0000000000000000, expected 000000000023FB70

1 0

Re: [PATCH 4/6] qcap: Constify vtables in Avi Mux tests
by Marvin 26 Nov '13

26 Nov '13

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=3548 Your paranoid android. === w8 (32 bit qcap) === qcap.c:1149: Test failed: ReceiveConnection returned 80040200 qcap.c:1152: Test failed: ConnectedTo returned 80040209 qcap.c:1153: Test failed: incorrect pin: 00000000, expected 0023FD64 === w864 (32 bit qcap) === qcap.c:1149: Test failed: ReceiveConnection returned 80040200 qcap.c:1152: Test failed: ConnectedTo returned 80040209 qcap.c:1153: Test failed: incorrect pin: 00000000, expected 0028FD54 === w864 (64 bit qcap) === qcap.c:1149: Test failed: ReceiveConnection returned 80040200 qcap.c:1152: Test failed: ConnectedTo returned 80040209 qcap.c:1153: Test failed: incorrect pin: 0000000000000000, expected 000000000023FB60

1 0

Re: [PATCH 3/6] qcap: Add Avi Mux input pin ReceiveConnection test
by Marvin 26 Nov '13

26 Nov '13

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=3547 Your paranoid android. === w8 (32 bit qcap) === qcap.c:1149: Test failed: ReceiveConnection returned 80040200 qcap.c:1152: Test failed: ConnectedTo returned 80040209 qcap.c:1153: Test failed: incorrect pin: 00000000, expected 0023FD64 === w864 (32 bit qcap) === qcap.c:1149: Test failed: ReceiveConnection returned 80040200 qcap.c:1152: Test failed: ConnectedTo returned 80040209 qcap.c:1153: Test failed: incorrect pin: 00000000, expected 0028FD54 === w864 (64 bit qcap) === qcap.c:1149: Test failed: ReceiveConnection returned 80040200 qcap.c:1152: Test failed: ConnectedTo returned 80040209 qcap.c:1153: Test failed: incorrect pin: 0000000000000000, expected 000000000023FB60

1 0

Re: [2/4] wininet: Reset data stream for existing request connections. (try 4)
by Marvin 25 Nov '13

25 Nov '13

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=3543 Your paranoid android. === w2008s64 (64 bit http) === http.c:3615: Test failed: HttpQueryInfo failed 0 === w7pro64 (64 bit http) === http.c:3615: Test failed: HttpQueryInfo failed 0

1 0

Re: [1/4] wininet/tests: Test successive HttpSendRequest calls. (try 4)
by Marvin 25 Nov '13

25 Nov '13

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=3542 Your paranoid android. === w2008s64 (64 bit http) === http.c:3615: Test failed: HttpQueryInfo failed 0 === w7pro64 (64 bit http) === http.c:3615: Test failed: HttpQueryInfo failed 0

1 0

Re: First try to sync translations with Transifex.com
by Francois Gouget 25 Nov '13

25 Nov '13

The attachment seems to have been mangled: when I looked at it here I only got question marks in the translations. So unless the mangling only happened here, that would be one reason why the patch has not been applied. Also, although the translation comes from Transifex.com, it looks like you're the only author behind the changes in that patch, i.e. there's presumably no copyright attribution issue. That may be worth noting in the patch submission. Could you resubmit your patch? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ 1 + e ^ ( i * pi ) = 0

2 1

Re: [PATCH 3/5] wined3d: Get rid of surface_set_dirty().
by Stefan Dösinger 25 Nov '13

25 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 2013-11-25 12:31, schrieb Henri Verbeet: > static void texture2d_sub_resource_add_dirty_region(struct > wined3d_resource *sub_resource, const struct wined3d_box > *dirty_region) { - > surface_set_dirty(surface_from_resource(sub_resource)); + struct > wined3d_surface *surface = surface_from_resource(sub_resource); + + > surface_load_location(surface, SFLAG_INSYSMEM); + > surface_invalidate_location(surface, ~SFLAG_INSYSMEM); } Why not something like if (surface->flags & SFLAG_INSYSMEM) surface_invalidate_location(surface, ~SFLAG_INSYSMEM); If the surface doesn't have SFLAG_INSYSMEM set already downloading texture / framebuffer data to sysmem and re-uploading it won't do anything. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSk0bMAAoJEN0/YqbEcdMw1rkP/R4WwqON6LvqMeZo1p37QJnA FmSC16ChtjbraQEJU9BkAbFZJCn1U8jiEybeUl3aayf3T5/OL+tk1eAbuUovuHtf LnOgCL8gHxUitao9kwPgM5gO4gwzo4IfT/kHKZ9/gu1FxqvHZGk/5khgXU67mAJ0 pp3SOhWPTbWu23k/ld6CQvp47DcFbEWoSn3n+20npv2OYGvmcUgVumW8EZIHhN8g EFou2wEKVoeEVyaPZzo85Cauv/nwyvwzJgZAgnRj5cokOu0AEpitf8jTqp2mXq6E V0ozMW5X40l6GkmrsVbHYoEhD6l+cX3Mf30b3WttHUrSd2XHDFqUHs8yONK/KxsV 7VT4zsh8vhWSqQFLp3e7ygNiryojHTBy9gC0eC5ahK9bbjkPpvHIrbj9+sHh58rP GXwAsLcxBLS0FofB2tk6zOYMILhRKWX6PhlldvsZVqvIN0mdAR/NTMoOyre7kxGf pCt/o8yXQZY/ujq3ZoKUXSjzFcV2ilhJq1EoiixCXR+X23Ge3s5WDfnPPe8QWeIZ Bl1wfVHtl9PQPL8Q5kb2g9xr572+J+HPLthT1kz73jHZ6VKSE3xN/c0vW3zzdfaJ OZRWfzmPOcAk+RqQUD3Ko2T7j/voLUH9sU3MD4FtPLfKKsOne4OMstt4VIQ/Qe5k tpOd6QkmBeS0Wq4mHywu =MNOz -----END PGP SIGNATURE-----

2 4

Re: [website] Portuguese translation for release 1.7.7
by Bruno Jesus 25 Nov '13

25 Nov '13

2013/11/25 Lucas Zawacki <lfzawacki(a)gmail.com>: > From: Lucas Zawacki <lfzawacki(a)gmail.com> > > --- > news/pt/2013112201.xml | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > create mode 100644 news/pt/2013112201.xml > > diff --git a/news/pt/2013112201.xml b/news/pt/2013112201.xml > new file mode 100644 > index 0000000..3fbff21 > --- /dev/null > +++ b/news/pt/2013112201.xml > @@ -0,0 +1,15 @@ > +<news> > +<date>22 de Novembro de 2013</date> > +<title>Wine 1.7.7 lançado</title> > +<body> > + A versão de desenvolvimento 1.7.7 já está disponível agora. > + <a href="{$root}/announce/1.7.7">Novidades</a> desta versão: > +<ul> > + <li>Suporte a configuração de comportilhamente remote usando a biblioteca NetAPI do Samba.</li> The word "remote" was not translated. > + <li>Suporte a múltiplos layouts de teclado no driver de Mac.</li> > + <li>Melhor suporte a uso embutido com XEMBED.</li> > + <li>Suporte a arrays em VBScript.</li> > + <li>Várias correções de bugs.</li> > +O código fonte está <a href="http://prdownloads.sourceforge.net/wine/wine-1.7.7.tar.bz2">disponível agora</a>. > +Pacotes binários estão em processo de construção e irão aparecer em breve em suas respectivas <a href="{$root}/download">sessões da área de downloads</a>. > +</body></news> > -- > 1.7.10.4 Best wishes, Bruno

1 0

Re: mshtml: Ignore QI(&IID_IWebBrowserPriv2IE8XP) calls.
by Marvin 25 Nov '13

25 Nov '13

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=3537 Your paranoid android. === wvista (32 bit htmldoc) === No test summary line found === w7pro64 (32 bit htmldoc) === No test summary line found === w8 (32 bit htmldoc) === htmldoc.c:2872: Test failed: unexpected command 74

1 0

Re: [PATCH 2/5] qmgr: Implement IBackgroundCopyJob::GetDescription()
by Dmitry Timoshkov 25 Nov '13

25 Nov '13

Nikolay Sivov <nsivov(a)codeweavers.com> wrote: > +static HRESULT return_strval(const WCHAR *str, WCHAR **ret) > +{ > + int len; > + > + if (!ret) return E_INVALIDARG; > + > + len = strlenW(str); > + *ret = CoTaskMemAlloc((len+1)*sizeof(WCHAR)); > + if (!*ret) return E_OUTOFMEMORY; > + > + if (len) > + strcpyW(*ret, str); > + else > + **ret = 0; > + return S_OK; > +} > + > static inline BackgroundCopyJobImpl *impl_from_IBackgroundCopyJob2(IBackgroundCopyJob2 *iface) > { > return CONTAINING_RECORD(iface, BackgroundCopyJobImpl, IBackgroundCopyJob2_iface); > @@ -313,17 +330,10 @@ static HRESULT WINAPI BITS_IBackgroundCopyJob_GetDisplayName( > LPWSTR *pVal) > { > BackgroundCopyJobImpl *This = impl_from_IBackgroundCopyJob2(iface); > - int n; > > - if (!pVal) > - return E_INVALIDARG; > + TRACE("(%p)->(%p)\n", This, pVal); > > - n = (strlenW(This->displayName) + 1) * sizeof **pVal; > - *pVal = CoTaskMemAlloc(n); > - if (*pVal == NULL) > - return E_OUTOFMEMORY; > - memcpy(*pVal, This->displayName, n); > - return S_OK; > + return return_strval(This->displayName, pVal); > } What is the reason of changing pVal type from LPWSTR* to WCHAR** in the helper? Leaving would LPWSTR* make it more clear IMO what the helper is supposed to do and would simplify dereferencing logic a bit. Also moving the parameter checks from the callers to helper doesn't look justified IMO. -- Dmitry.

2 1

Re: quartz/tests: Add tests for IVMRMonitorConfig and IVMRMonitorConfig9 interface (try 2)
by Nikolay Sivov 25 Nov '13

25 Nov '13

On 11/25/2013 10:23, Sebastian Lackner wrote: > + hr = CoCreateInstance(&CLSID_VideoRenderer, NULL, CLSCTX_INPROC_SERVER, > + &IID_IUnknown, (LPVOID*)&pVideoRenderer); > + ok(hr != S_OK || pVideoRenderer != NULL, "CoCreateInstance returned S_OK, but pVideoRenderer is NULL.\n"); > + if (hr != S_OK || !pVideoRenderer) > + { > + skip("VideoRenderer is not available, skipping QI test.\n"); > + return; > + } > + > QI_SUCCEED(pVideoRenderer, IID_IBaseFilter, pBaseFilter); > RELEASE_EXPECT(pBaseFilter, 1); It's enough to test for return value, also if wine supports this class this should be win_skip(). What's a point of separate QI here? You could CoCreateInstance with IID_IBaseFilter. > + hr = IUnknown_QueryInterface(pVMR7, &IID_IVMRMonitorConfig, (LPVOID*)&pMonitorConfig); > + ok(hr == S_OK, "IUnknown_QueryInterface returned %x.\n", hr); > + ok(pMonitorConfig != NULL, "pMonitorConfig is NULL.\n"); > + if (!pMonitorConfig) goto out; Is it really possible to fail here? > + ok(info[numdev].guid.pGUID != &info[numdev].guid.GUID || memcmp(&info[numdev].guid.GUID, &max_guid, sizeof(max_guid)) != 0, > + "GetAvailableMonitors returned info[%d].GUID = {FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF}, expected any other value.\n", numdev); It's shorter to just print resulting guid. > + /* check that result is filled out, we do not check if the values actually make any sense */ > + while (numdev--) > + { > + ok(info[numdev].uDevID != (UINT)-1, > + "GetAvailableMonitors returned info[%d].uDevID = -1, expected != -1.\n", numdev); > + ok(memcmp(&info[numdev].rcMonitor, &max_rect, sizeof(max_rect)) != 0, > + "GetAvailableMonitors returned info[%d].rcMonitor = {-1, -1, -1, -1}, expected any other value.\n", numdev); > + ok(info[numdev].hMon != (HMONITOR)0 && info[numdev].hMon != (HMONITOR)-1, > + "GetAvailableMonitors returned info[%d].hMon = %p, expected != 0 and != -1.\n", numdev, info[numdev].hMon); > + ok(info[numdev].dwFlags != (DWORD)-1, > + "GetAvailableMonitors returned info[%d].dwFlags = -1, expected != -1.\n", numdev); > + ok(info[numdev].szDevice[0] != 0 && info[numdev].szDevice[0] != (WCHAR)-1, > + "GetAvailableMonitors returned info[%d].szDevice[0] = %d, expected != 0 and != -1.\n", numdev, info[numdev].szDevice[0]); > + todo_wine ok(info[numdev].szDescription[0] != 0 && info[numdev].szDescription[0] != (WCHAR)-1, > + "GetAvailableMonitors returned info[%d].szDescription[0] = %d, expected != 0 and != -1.\n", numdev, info[numdev].szDescription[0]); > + ok(info[numdev].dwVendorId != (DWORD)-1, > + "GetAvailableMonitors returned info[%d].dwVendorId = -1, expected != -1.\n", numdev); > + ok(info[numdev].dwDeviceId != (DWORD)-1, > + "GetAvailableMonitors returned info[%d].dwDeviceId = -1, expected != -1.\n", numdev); > + ok(info[numdev].dwSubSysId != (DWORD)-1, > + "GetAvailableMonitors returned info[%d].dwSubSysId = -1, expected != -1.\n", numdev); > + ok(info[numdev].dwRevision != (DWORD)-1, > + "GetAvailableMonitors returned info[%d].dwRevision = -1, expected != -1.\n", numdev); > + } Personally I don't like this, I think this should be more explicit - set fields separately to some invalid value that shouldn't happen and check it back. For example for string field it makes no sense setting it to -1 if it's always filled.

1 0

Re: vbscript: Added support for VT_BYREF|VT_VARIANT to to_int.
by Marvin 22 Nov '13

22 Nov '13

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=3510 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 === w8 (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: [2/3] wininet: Reset data stream for existing request connections.
by Marvin 22 Nov '13

22 Nov '13

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=3506 Your paranoid android. === w2008s64 (64 bit http) === http.c:3615: Test failed: HttpQueryInfo failed 0 === w7pro64 (64 bit http) === http.c:3615: Test failed: HttpQueryInfo failed 0

1 0

Re: [1/3] wininet/tests: Test successive HttpSendRequest calls.
by Marvin 22 Nov '13

22 Nov '13

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=3505 Your paranoid android. === w7pro64 (32 bit http) === http.c:4450: Test failed: HttpSendRequest failed: 12057 http.c:4455: Test failed: expected secure flag to be set === w2008s64 (64 bit http) === http.c:3615: Test failed: HttpQueryInfo failed 0 === w7pro64 (64 bit http) === http.c:3615: Test failed: HttpQueryInfo failed 0

1 0

Re: msvcrt: return wall-clock time from clock()
by Alexandre Julliard 22 Nov '13

22 Nov '13

Daniel Lehman <dlehman(a)esri.com> writes: > @@ -709,19 +711,26 @@ int CDECL _wstrtime_s(MSVCRT_wchar_t* time, MSVCRT_size_t size) > */ > MSVCRT_clock_t CDECL MSVCRT_clock(void) > { > - FILETIME ftc, fte, ftk, ftu; > - ULONGLONG utime, ktime; > - > - MSVCRT_clock_t clock; > + static LONGLONG start_time; > + LONGLONG current_time; > + struct timeval now; > > - GetProcessTimes(GetCurrentProcess(), &ftc, &fte, &ftk, &ftu); > + if(!start_time) { > + KERNEL_USER_TIMES pti; > > - ktime = ((ULONGLONG)ftk.dwHighDateTime << 32) | ftk.dwLowDateTime; > - utime = ((ULONGLONG)ftu.dwHighDateTime << 32) | ftu.dwLowDateTime; > + /* while Linux's clock returns user time, Windows' clock > + * returns wall-clock time from process start. cache the > + * process start time since it won't change and to avoid > + * wineserver round-trip overhead */ > + if(NtQueryInformationProcess(GetCurrentProcess(), ProcessTimes, &pti, sizeof(pti), NULL)) > + return -1; > + start_time = pti.CreateTime.QuadPart; > + } > > - clock = (utime + ktime) / (TICKSPERSEC / MSVCRT_CLOCKS_PER_SEC); > + gettimeofday(&now, NULL); > + current_time = (LONGLONG)now.tv_sec * TICKSPERSEC + now.tv_usec * 10 + TICKS_1601_TO_1970; You should be using Windows APIs for this, not gettimeofday. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH] ddraw: add dsurface dimension tests, try 3
by Henri Verbeet 22 Nov '13

22 Nov '13

Stefan already mentioned this, although perhaps not quite as explicit, but new ddraw tests need to go to ddraw1-7.c. In this specific case, the best option is probably to first move SizeTest() over to ddraw1-7.c (and rename it to test_surface_size(), fix minor style issues etc.), and then add the new tests after that.

1 0

Re: gdiplus: Implement GdipCreateRegionRgnData. Take 2.
by Alexandre Julliard 22 Nov '13

22 Nov '13

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > This version of the patch follows Windows behaviour by refusing to create > an empty path in a region, and marks the test as broken when some Windows > versions fail to properly clear an aligned DWORD. > --- > dlls/gdiplus/region.c | 219 ++++++++++++++++++++++++++++++++++++++++---- > dlls/gdiplus/tests/region.c | 65 +++++++++++++ > 2 files changed, 266 insertions(+), 18 deletions(-) > > diff --git a/dlls/gdiplus/region.c b/dlls/gdiplus/region.c > index 832ce69..bc625f5 100644 > --- a/dlls/gdiplus/region.c > +++ b/dlls/gdiplus/region.c > @@ -76,6 +76,28 @@ WINE_DEFAULT_DEBUG_CHANNEL(gdiplus); > #define FLAGS_NOFLAGS 0x0 > #define FLAGS_INTPATH 0x4000 > > +struct _memory_buffer > +{ > + const BYTE *buffer; > + INT size, pos; > +}; > + > +struct _region_header > +{ > + DWORD size; > + DWORD checksum; > + DWORD magic; > + DWORD num_children; > +}; > + > +struct _path_header > +{ > + DWORD size; > + DWORD magic; > + DWORD count; > + DWORD flags; > +}; There's no need to add leading underscores, it's obvious that these are not Windows types. -- Alexandre Julliard julliard(a)winehq.org

4 10

__wine_spec_nt_header: relocation truncated to fit: R_386_PC16 against undefined symbol
by Gerald Pfeifer 22 Nov '13

22 Nov '13

My last two nightly boostraps on FreeBSD have started to fail as follows: ../../tools/winegcc/winegcc -B../../tools/winebuild --sysroot=../.. -fasynchronous-unwind-tables -shared ./sound.drv16.spec -m16 -Wb,--main-module,winmm.dll sound.o -o sound.drv16.so -lwine ../../libs/port/libwine_port.a -L/home/gerald/10-i386/lib sound.drv16-5l5JpE.spec.o: In function `__wine_spec_nt_header': (.data+0x48c): relocation truncated to fit: R_386_PC16 against undefined symbol `.L__wine_spec_callfrom16_p_long_' collect2: error: ld returned 1 exit status winegcc: /home/gerald/gcc-ref10-i386/bin/gcc failed gmake: *** [sound.drv16.so] Error 2 Originally I thought this was the top of tree nightly GCC builds I am using, but today I also go it with GCC 4.8.3 20131121 (prerelease). Any ideas what might be going on here? Any tips how to best debug this? Gerald

1 0

Re: mscoree: Implement IMetahostPolicy GetRequestedRuntime
by Vincent Povirk 21 Nov '13

21 Nov '13

+ else if(pwzBinary && lstrlenW(pwzBinary) > 0) Did you really need the check for an empty string? This is making me wonder if my comment on bugzilla was wrong, and get_runtime_info should treat an empty string the same as NULL.

1 0

Re: wininet: Reading past end-of-file in chunked mode returns success.
by Marvin 21 Nov '13

21 Nov '13

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=3497 Your paranoid android. === w2008s64 (64 bit http) === http.c:3525: Test failed: HttpQueryInfo failed 0 === w7pro64 (64 bit http) === http.c:3525: Test failed: HttpQueryInfo failed 0

1 0

Re: xcopy: Add tests to show that the /D option only accepts dates in the m-d-y format.
by Marvin 21 Nov '13

21 Nov '13

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=3495 Your paranoid android. === build (build) === Recreation of tests/Makefile failed

1 0

Re: [2/3] wininet: Reset data stream for existing request connections.
by Marvin 21 Nov '13

21 Nov '13

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=3494 Your paranoid android. === w2008s64 (64 bit http) === http.c:3610: Test failed: HttpQueryInfo failed 0 === w7pro64 (64 bit http) === http.c:3610: Test failed: HttpQueryInfo failed 0

1 0

Re: [1/3] wininet/tests: Test successive HttpSendRequest calls. (try 2)
by Marvin 21 Nov '13

21 Nov '13

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=3493 Your paranoid android. === w2008s64 (64 bit http) === http.c:3610: Test failed: HttpQueryInfo failed 0 === w7pro64 (64 bit http) === http.c:3610: Test failed: HttpQueryInfo failed 0

1 0

Re: po: xcopy expects a date in the French locale format for the /D option.
by Francois Gouget 21 Nov '13

21 Nov '13

On Thu, 21 Nov 2013, Francois Gouget wrote: > --- > > Of course Wine does not yet implement the /D option but when it does it > will have to match the Windows implementation so the documentation > might as well be correct from the start. Please ignore this patch. On Windows XP and 7 alike Microsoft's xcopy does say: | /D:j-m-a Copie les fichiers modifiés à partir de la date spécifiée But on both systems it refuses a date of 21-11-2013 but accepts 11-21-2013. So once more the Microsoft documentation is wrong. c:\Users\win7admin\Documents> xcopy /D:21-11-2013 *.* tmp Paramètre non valide - /D:21-11-2013 c:\Users\win7admin\Documents> xcopy /D:21-11-2013 *.* tmp c:foo 1 fichier(s) copié(s) -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ If it stinks, it's chemistry. If it moves, it's biology. If it does not work, it's computer science.

1 0

Re: [PATCH 2/2] winemac: Add support for a DisableWindowDecorations registry setting.
by Alexandre Julliard 21 Nov '13

21 Nov '13

Ken Thomases <ken(a)codeweavers.com> writes: > @@ -166,6 +167,9 @@ static void setup_options(void) > if (!get_config_key(hkey, appkey, "AllowSoftwareRendering", buffer, sizeof(buffer))) > allow_software_rendering = IS_OPTION_TRUE(buffer[0]); > > + if (!get_config_key(hkey, appkey, "DisableWindowDecorations", buffer, sizeof(buffer))) > + disable_window_decorations = IS_OPTION_TRUE(buffer[0]); > + Disable-style options should be avoided, the double negatives are confusing for users. Also using the same option name as the X11 driver for the same feature may be a good idea. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [2/3] wininet: Reset data stream for existing request connections.
by Marvin 21 Nov '13

21 Nov '13

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=3486 Your paranoid android. === wxppro (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === wvista (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w2008s64 (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w7pro64 (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w8 (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w864 (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w2008s64 (64 bit http) === http.c:3606: Test failed: HttpQueryInfo failed 0 http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w7pro64 (64 bit http) === http.c:3606: Test failed: HttpQueryInfo failed 0 http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w864 (64 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT)

1 0

Re: [1/3] wininet/tests: Test successive HttpSendRequest calls.
by Marvin 21 Nov '13

21 Nov '13

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=3485 Your paranoid android. === wxppro (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === wvista (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w2008s64 (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w7pro64 (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w8 (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w864 (32 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w2008s64 (64 bit http) === http.c:3606: Test failed: HttpQueryInfo failed 0 http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w7pro64 (64 bit http) === http.c:3606: Test failed: HttpQueryInfo failed 0 http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT) === w864 (64 bit http) === http.c:318: Test failed: unexpected status 320 (INTERNET_STATUS_COOKIE_SENT)

1 0

Re: [PATCH 3/3] ws2_32: Add an interactive test for interface change notifications (resend).
by Marvin 20 Nov '13

20 Nov '13

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=3480 Your paranoid android. === wxppro (32 bit sock) === sock.c:520: Test failed: oob_server (174): unexpectedly at the OOB mark: 0 sock: unhandled exception c0000005 at 71AB91B2 === w2008s64 (32 bit sock) === sock.c:520: Test failed: oob_server (768): unexpectedly at the OOB mark: 0 sock: unhandled exception c0000005 at 757C9799 === w7pro64 (32 bit sock) === sock.c:529: Test failed: oob_server (96c): not at the OOB mark: 1 === w864 (32 bit sock) === sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1748: Test failed: getservbyname: winsock resized servent buffer when not necessary sock.c:1748: Test failed: getservbyname: winsock resized servent buffer when not necessary === w2008s64 (64 bit sock) === sock.c:510: Test failed: oob_server (654): unexpectedly at the OOB mark: 0 sock.c:520: Test failed: oob_server (654): unexpectedly at the OOB mark: 0

1 0

Re: [PATCH 5/5] qcap: Add AVI Mux QueryInterface tests
by Marvin 20 Nov '13

20 Nov '13

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=3479 Your paranoid android. === build (build) === Make failed

1 0

Re: [PATCH 6/6] winemac: Actually set the system's keyboard layout.
by Ken Thomases 20 Nov '13

20 Nov '13

On Nov 20, 2013, at 9:30 AM, Huw Davies wrote: > --- > dlls/winemac.drv/cocoa_app.m | 11 ++++++ > dlls/winemac.drv/keyboard.c | 80 +++++++++-------------------------------- > dlls/winemac.drv/macdrv_cocoa.h | 1 + > 3 files changed, 29 insertions(+), 63 deletions(-) > > <0006-winemac-Actually-set-the-system-s-keyboard-layout.patch> Series looks good to me. -Ken

1 0

Re: mscoree: Attempt to load the assembly from the application directory (try 3)
by Vincent Povirk 20 Nov '13

20 Nov '13

Looks good to me.

1 0

Re: [PATCH 5/5] d3d8/tests: Add a test for AddDirtyRect.
by Marvin 20 Nov '13

20 Nov '13

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=3472 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: [PATCH 4/5] d3d9/tests: Add a test for AddDirtyRect.
by Marvin 20 Nov '13

20 Nov '13

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=3471 Your paranoid android. === build (build) === Patch failed to apply

1 0

Re: ws2_32/tests: Mark the out of bound results we don't want to support as broken
by Marvin 19 Nov '13

19 Nov '13

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=3467 Your paranoid android. === w2008s64 (32 bit sock) === sock: unhandled exception c0000005 at 757C9799 === w864 (64 bit sock) === sock.c:1741: Test failed: sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for telnet: 11004 sock.c:1741: Test failed: getservbyname could not retrieve information for domain: 11004 sock.c:1748: Test failed: getservbyname: winsock resized servent buffer when not necessary

1 0

Re: shell32/tests: delete a nonexistent file in an existent dir or a nonexistent dir (try 2)
by Lauri Kenttä 19 Nov '13

19 Nov '13

On 2013-11-19 03:17, Zhenbo Li wrote: > + broken(ret == 0x402), /* XP */ > + "Expected 1027 or DE_INVALIDFILES, got %d\n", ret); Looks like you accidentally changed this one to 1027 instead of 0x402. -- Lauri Kenttä Reply-To: wine-devel(a)winehq.org

2 1

AUTHORS: Revert commit 5da31c8817293ff98b4defceb962f7d0fbc25829 (Was: How to undo authors list generated automatically.)
by Tae Wong 19 Nov '13

19 Nov '13

You want to revert the commit 5da31c8817293ff98b4defceb962f7d0fbc25829. Quintana said that it's a suggestion for it. Some Portuguese last names sorted under first instead of second element! See blob e69040d889c1748d538f1198f6c85b97f55418b5. Araujo Chaves, Pedro, Jr Arcoverde da Rocha, Augusto Castro Lopo, Erik de Example of Portuguese last names sorted by the second element: Chaves, Pedro Araujo, Jr Lopo, Erik de Castro Rocha, Augusto Arcoverde da

1 1

Re: shell32/tests: Change Dec to Hex
by Lauri Kenttä 19 Nov '13

19 Nov '13

On 2013-11-19 18:03, Zhenbo Li wrote: > + "Expected 0x402 or ERROR_FILE_NOT_FOUND, got %d\n", retval); You should probably change the %d to %x, too. On the other hand, I don't see any need for your patch whatsoever. Maybe you should explain yourself. -- Lauri Kenttä

4 3

Re: [2/2] quartz/tests: Add tests for IVMRMonitorConfig and IVMRMonitorConfig9 interface
by Alexandre Julliard 19 Nov '13

19 Nov '13

Sebastian Lackner <sebastian(a)fds-team.de> writes: > diff --git a/dlls/quartz/tests/Makefile.in b/dlls/quartz/tests/Makefile.in > index ae5fbac..94b2f44 100644 > --- a/dlls/quartz/tests/Makefile.in > +++ b/dlls/quartz/tests/Makefile.in > @@ -8,6 +8,7 @@ C_SRCS = \ > filtermapper.c \ > memallocator.c \ > misc.c \ > + monitorconfig.c \ > referenceclock.c \ > videorenderer.c Please merge it into one of the existing files. -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: shell32/tests: Change Dec to Hex
by Zhenbo Li 19 Nov '13

19 Nov '13

Sorry, something was wrong with my network, so I had send my patch twice. 2013/11/20 Zhenbo Li <litimetal(a)gmail.com>: > --- > dlls/shell32/tests/shlfileop.c | 22 +++++++++++----------- > 1 file changed, 11 insertions(+), 11 deletions(-) > > -- Have a nice day! Zhenbo Li

1 0

Re: [PATCH] ddraw: add dsurface dimension tests, try 2
by Patrick Rudolph 19 Nov '13

19 Nov '13

Am 2013-11-18 16:44, schrieb Stefan Dösinger: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > Overall, did you check if there is a capability reporting problem? The > game may have the bad size from our DDSCAPS structure. > I'm not sure. It successfully creates a primary surface with dimension 320x240 and it creates offscreen surfaces with dimension 320x240 and DDSCAPS_SYSTEMMEMORY flag set. Only offscreen surfaces with DDSCAPS_VIDEOMEMORY flag set are out of range. I was wondering: 15728640 = 320 << 16 and 20971520 = 240 << 16. Where does the two byte offset come from ? > Even if this is a capability problem I think this test is relevant. > > Am 2013-11-17 20:19, schrieb Patrick Rudolph: >> dlls/ddraw/tests/dsurface.c | 88 > +++++++++++++++++++++++++++++++++++++++++++++ > > Please add new tests to ddraw{1, 2, 4, 7}.c, and if possible implement > them for all ddraw versions. I can do that as well. > >> + ZeroMemory(&desc, sizeof(desc)); > memset(desc, 0, sizeof(desc)); is preferred. > >> + if(!(ddcaps.ddsCaps.dwCaps & DDSCAPS_VIDEOMEMORY)) + { + >> todo_wine ok(ret == DDERR_INVALIDPARAMS, "Creating an > offscreen plain surface with width 0xffff and height 1 returned > %08x\n", ret); >> + } > Is there any situation in which wine enters this codepath? I think the > todo_wine is not needed here. You are right, wine always presents a direct draw device with DDSCAPS_VIDEOMEMORY. I removed ligGL, ddraw still "works", but doesn't render anything. > >> + /* Test out of memory surface size */ + ZeroMemory(&desc, >> sizeof(desc)); + desc.dwSize = sizeof(desc); + desc.dwFlags = >> DDSD_CAPS | DDSD_HEIGHT | DDSD_WIDTH; + desc.ddsCaps.dwCaps |= >> DDSCAPS_OFFSCREENPLAIN | > DDSCAPS_VIDEOMEMORY; >> + desc.dwHeight = 0xffff; + desc.dwWidth = 0xffff; + /* >> this should allocate 4.29 Gbyte of video memory */ > Testing DDSCAPS_SYSTEMMEMORY might show some interesting results as > well, especially in a Win64 executable. > I can add tests for this. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBAgAGBQJSijXyAAoJEN0/YqbEcdMwolYP+wWH7o7Dn9LjmjJq0dca5ZD9 > EKfyGNxrtg/Th1o2qKdP4rmsl1G8UC96Xo2BP9Fi5tH9BZTzAXTiq2pfSiKGf0Z7 > l48UbVGVuVd/nxBG8ULZDS7e8b9h+NwcprM3flWW6frbqsDMxf1LPhtNsEQU8gnE > 0/hFXW/T33FkPP3XiBK6vCgWjP1umK9clcQHvit7DitFpFBmwOj5SxktoIsoPVpL > TcOiaaXKcABTbKCz4xclOaAMM7k94cH0ByJBVu+8OXNTOHzd0xbtrnFl6UZi74jH > dQyqLIyQ4uDs1760He7WtwgMEeF4NhV+u3A6qRP3eLceSf59OhEhSUNGKu5yduVb > F16yGgQiTIKHpqtD1sT1RPEDAZgUYL9Uq8BnUrPbNZ+FJI5ZwIbY7KghozAhUweA > /TC9VMLwUnJKk8v/8xHPY1WI3474Pht4joahUNWkTQ8QuN7ms44IyyyALBsWM3gF > eOSTBNEcWZz+3uRaS68/ZDeqzo+R+dwmwU8XTeWEMTxuy30x1OdCTp3BgR8YNXMa > 2uLWa5mL4pkOAVJ6gI6HHPpX8T582lB3PcZgRMd5QirwIg76dwvnk6zpiv4RqFS5 > 3HCCey4c3FO4aFhDcelkNsdcpCMbaGyv4lqtLDzBe7bR5xOrtWvmdl5r3vvlCbO2 > uERNPhePZ8ogI6buwboM > =v8j0 > -----END PGP SIGNATURE-----

2 1

Re: gdiplus: Implement GdipCreateRegionRgnData. Take 2.
by Vincent Povirk 19 Nov '13

19 Nov '13

Please note that most of this format (everything except the first 8 bytes of region_header) is documented in MS-EMFPLUS section 2.2.1.8: http://msdn.microsoft.com/en-us/library/cc230724.aspx + switch (path_header->flags & FLAGS_INTPATH) You should check for other flags here, namely 0x1000 which indicates RLE compression of point types and 0x0400 which indicates that points are relative to the previous point. (Not saying we need to support them initially, but please check so we know if they appear. Also, the lower 16 bits other than those flags are supposed to always be 0, so maybe we should check them for unknown values as well.) + if (!region_header || region_header->magic != VERSION_MAGIC) + return InvalidParameter; This should also accept 0xdbc01002, for GDI+ version 1.1. + if (i == 1) continue; /* data[1] never matches */ If that's the case, shouldn't you have a test that it doesn't match?

2 5

Re: Assorted spelling fixes.
by Jonas Maebe 19 Nov '13

19 Nov '13

On 18 Nov 2013, at 20:34, Frédéric Delanoy wrote: > --- a/dlls/ole32/itemmoniker.c > +++ b/dlls/ole32/itemmoniker.c > @@ -123,7 +123,7 @@ static ULONG WINAPI ItemMonikerImpl_Release(IMoniker* iface) > > ref = InterlockedDecrement(&This->ref); > > - /* destroy the object if there's no more reference on it */ > + /* destroy the object if there are no moee references on it */ "no more" instead of "moee". I would also say "no more references to it" instead of "on it". Jonas

2 1

Re: shell32/tests: delete a nonexistent file in an existent dir or a nonexistent dir
by Nikolay Sivov 18 Nov '13

18 Nov '13

On 11/18/2013 20:12, Zhenbo Li wrote: > I found that shell32 test hasn't covered DE_INVALIDFILES > --- > dlls/shell32/tests/shlfileop.c | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > + ret = SHFileOperationA(&shfo); > + todo_wine > + ok(ret == 1026 || > + ret == ERROR_FILE_NOT_FOUND || /* Vista */ > + broken(ret == ERROR_SUCCESS), /* NT4 */ > + "Expected 1026 or ERROR_FILE_NOT_FOUND, got %d\n", ret); I think it's safe to mark XP result broken() as well. Also please use 0x402 value here for it, it's easier to find this way.

1 0

Re: [PATCH] ddraw: add dsurface dimension tests, try 2
by Stefan Dösinger 18 Nov '13

18 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Overall, did you check if there is a capability reporting problem? The game may have the bad size from our DDSCAPS structure. Even if this is a capability problem I think this test is relevant. Am 2013-11-17 20:19, schrieb Patrick Rudolph: > dlls/ddraw/tests/dsurface.c | 88 +++++++++++++++++++++++++++++++++++++++++++++ Please add new tests to ddraw{1, 2, 4, 7}.c, and if possible implement them for all ddraw versions. > + ZeroMemory(&desc, sizeof(desc)); memset(desc, 0, sizeof(desc)); is preferred. > + if(!(ddcaps.ddsCaps.dwCaps & DDSCAPS_VIDEOMEMORY)) + { + > todo_wine ok(ret == DDERR_INVALIDPARAMS, "Creating an offscreen plain surface with width 0xffff and height 1 returned %08x\n", ret); > + } Is there any situation in which wine enters this codepath? I think the todo_wine is not needed here. > + /* Test out of memory surface size */ + ZeroMemory(&desc, > sizeof(desc)); + desc.dwSize = sizeof(desc); + desc.dwFlags = > DDSD_CAPS | DDSD_HEIGHT | DDSD_WIDTH; + desc.ddsCaps.dwCaps |= > DDSCAPS_OFFSCREENPLAIN | DDSCAPS_VIDEOMEMORY; > + desc.dwHeight = 0xffff; + desc.dwWidth = 0xffff; + /* > this should allocate 4.29 Gbyte of video memory */ Testing DDSCAPS_SYSTEMMEMORY might show some interesting results as well, especially in a Win64 executable. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSijXyAAoJEN0/YqbEcdMwolYP+wWH7o7Dn9LjmjJq0dca5ZD9 EKfyGNxrtg/Th1o2qKdP4rmsl1G8UC96Xo2BP9Fi5tH9BZTzAXTiq2pfSiKGf0Z7 l48UbVGVuVd/nxBG8ULZDS7e8b9h+NwcprM3flWW6frbqsDMxf1LPhtNsEQU8gnE 0/hFXW/T33FkPP3XiBK6vCgWjP1umK9clcQHvit7DitFpFBmwOj5SxktoIsoPVpL TcOiaaXKcABTbKCz4xclOaAMM7k94cH0ByJBVu+8OXNTOHzd0xbtrnFl6UZi74jH dQyqLIyQ4uDs1760He7WtwgMEeF4NhV+u3A6qRP3eLceSf59OhEhSUNGKu5yduVb F16yGgQiTIKHpqtD1sT1RPEDAZgUYL9Uq8BnUrPbNZ+FJI5ZwIbY7KghozAhUweA /TC9VMLwUnJKk8v/8xHPY1WI3474Pht4joahUNWkTQ8QuN7ms44IyyyALBsWM3gF eOSTBNEcWZz+3uRaS68/ZDeqzo+R+dwmwU8XTeWEMTxuy30x1OdCTp3BgR8YNXMa 2uLWa5mL4pkOAVJ6gI6HHPpX8T582lB3PcZgRMd5QirwIg76dwvnk6zpiv4RqFS5 3HCCey4c3FO4aFhDcelkNsdcpCMbaGyv4lqtLDzBe7bR5xOrtWvmdl5r3vvlCbO2 uERNPhePZ8ogI6buwboM =v8j0 -----END PGP SIGNATURE-----

2 1

Re: [PATCH 1/5] wined3d: Create a proper texture for the software cursor.
by Stefan Dösinger 18 Nov '13

18 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 2013-11-18 10:46, schrieb Henri Verbeet: > + desc.pool = WINED3D_POOL_SYSTEM_MEM; Why did you use this pool instead of managed or dynamic default to allow a GL blit? I haven't tested this, but I suspect the WINEDDBLT_KEYSRC hack won't work in a software blit. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSihI1AAoJEN0/YqbEcdMwAN4P/iRR8C1ctmY2Eu/FUORAIcmr IFDOyZnxecPmM+0pEOX+W2RVrJmwPlnI8PDBwmKnqJNx80FxEWHIq4gTzS/InhGJ BykTeNTyb7YdHr76V6lZKr8TJTl0CaP8QWEtnl342lGBFaLjXbGbjN5Uf8v3Nv6O 3mBI0hHKvPB2gNtNfnQA2y+xhE/an0s1P0hAP6SE/BcdB9xZORCyBA5Iq1ajTBqz f9lpiIW8+9vApEEGF9wncikgvJR/snGY+JhzcxCPKg5sslDyhVBY3AgfGOR9y9IU xHgF+nN8G99MJKl/+xuvbAmcAKrltH9iR2VYBH0RtJRF0GvT9mVdbASybR6gak55 j39B+X4VpZor+6bZtaV/0+oGShxEqz4mIu6RwPQHCLL7c5IpRM3SnVmu2BQlTEhB j2SJ61P+uQdAEHAjfcl5blVuhbkPwsGA5m0oNRCRopxylbnYNbM00V8P37kkEg7D bMrs/LkP8QWN4lZoj9kZ4eR9TyvjSkSFL+5eKuULtZNlhUKfKrntBzwKfpuNJYxs 9icHe30boy4aHe0xfrVTcN9K6ALIzV4xmUgItWckjpmRTwOwEnen13tTXcKLmJWG 2CXZEz59sa7eEwc1A7NeIjKpf8EUGG34TIUJtcCT326dWRC32khXPzGKVvgqq94a 7G+ZaRaImayepVr0AKdn =ZJqZ -----END PGP SIGNATURE-----

2 3

Re: riched20: Implement ITextDocument_fnOpen. (try 2)
by Nikolay Sivov 18 Nov '13

18 Nov '13

On 11/18/2013 16:02, Jactry Zeng wrote: > update: > 1. Use 0 in HeapAlloc instead of HEAP_ZERO_MEMORY; > 2. Return an E_OUTOFMEMORY instead of HRESULT_FROM_WIN32(GetLastError()) > when HeapAlloc fail. > + FIXME("Don't support UTF-16.\n"); How is supposed to be handled? > + FIXME("Partial stub! Don't support flag: 0x%x\n", Flags); At least some flags are easy to support mapping them to sharing and creation disposition modes. > + chBuffer = HeapAlloc(GetProcessHeap(), 0, size+1); > + if(!chBuffer) > + { > + CloseHandle(hFile); > + return E_OUTOFMEMORY; > + } > + > + if(!ReadFile(hFile, chBuffer, size, &dwReadSize, NULL)) > + { > + CloseHandle(hFile); > + HeapFree(GetProcessHeap(), 0, chBuffer); > + return HRESULT_FROM_WIN32(GetLastError()); > + } > + chBuffer[size] = 0; How will it work for UTF-16 input? > + SendMessageW(This->editor->hWnd, EM_SETTEXTEX, (int)&settextex, (LPARAM)chBuffer); > + CloseHandle(hFile); > + > + return S_OK; Looks like you leak a buffer.

2 1

Re: gdiplus: Implement GdipCreateRegionRgnData.
by Marvin 18 Nov '13

18 Nov '13

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=3433 Your paranoid android. === wxppro (32 bit region) === region.c:438: Test failed: GdipCreateRegionRgnData error 1 === wvista (32 bit region) === region.c:438: Test failed: GdipCreateRegionRgnData error 1 === w2008s64 (32 bit region) === region.c:438: Test failed: GdipCreateRegionRgnData error 1 === w7pro64 (32 bit region) === region.c:438: Test failed: GdipCreateRegionRgnData error 1 region.c:623: Test failed: data mismatch region.c:774: Test failed: data mismatch === w8 (32 bit region) === region.c:438: Test failed: GdipCreateRegionRgnData error 1 region.c:623: Test failed: data mismatch region.c:774: Test failed: data mismatch === w864 (32 bit region) === region.c:438: Test failed: GdipCreateRegionRgnData error 1 region.c:623: Test failed: data mismatch region.c:774: Test failed: data mismatch === w2008s64 (64 bit region) === region.c:438: Test failed: GdipCreateRegionRgnData error 1 === w7pro64 (64 bit region) === region.c:438: Test failed: GdipCreateRegionRgnData error 1 region.c:774: Test failed: data mismatch === w864 (64 bit region) === region.c:438: Test failed: GdipCreateRegionRgnData error 1 region.c:774: Test failed: data mismatch

1 0

Re: [PATCH] ddraw: add dsurface dimension tests
by Marvin 17 Nov '13

17 Nov '13

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=3418 Your paranoid android. === wxppro (32 bit dsurface) === dsurface.c:2604: Test failed: Creating an offscreen plain surface with width 0xffff and height 1 returned 80070057 dsurface.c:2663: Test failed: Creating an offscreen plain surface with width 0xffff and height 0xffff returned 88760233 === wvista (32 bit dsurface) === dsurface.c:2604: Test failed: Creating an offscreen plain surface with width 0xffff and height 1 returned 80070057 dsurface.c:2663: Test failed: Creating an offscreen plain surface with width 0xffff and height 0xffff returned 88760233 === w2008s64 (32 bit dsurface) === dsurface.c:2604: Test failed: Creating an offscreen plain surface with width 0xffff and height 1 returned 80070057 dsurface.c:2663: Test failed: Creating an offscreen plain surface with width 0xffff and height 0xffff returned 88760233 === w7pro64 (32 bit dsurface) === dsurface.c:2604: Test failed: Creating an offscreen plain surface with width 0xffff and height 1 returned 80070057 dsurface.c:2663: Test failed: Creating an offscreen plain surface with width 0xffff and height 0xffff returned 88760233 === w8 (32 bit dsurface) === dsurface.c:2663: Test failed: Creating an offscreen plain surface with width 0xffff and height 0xffff returned 8876017c === w864 (32 bit dsurface) === dsurface.c:2663: Test failed: Creating an offscreen plain surface with width 0xffff and height 0xffff returned 8876017c === w2008s64 (64 bit dsurface) === dsurface.c:2604: Test failed: Creating an offscreen plain surface with width 0xffff and height 1 returned 80070057 dsurface.c:2663: Test failed: Creating an offscreen plain surface with width 0xffff and height 0xffff returned 88760233 === w7pro64 (64 bit dsurface) === dsurface.c:2604: Test failed: Creating an offscreen plain surface with width 0xffff and height 1 returned 80070057 dsurface.c:2663: Test failed: Creating an offscreen plain surface with width 0xffff and height 0xffff returned 88760233 === w864 (64 bit dsurface) === dsurface.c:2663: Test failed: Creating an offscreen plain surface with width 0xffff and height 0xffff returned 8876017c

1 0

Re: Use BOOL type where appropriate (Patches 100478 and 100479) are wrong for localspl
by Detlef Riekenberg 17 Nov '13

17 Nov '13

Hi Frederic. BOOL is not correct for localspl.dll. Next to 0 and 1 you can get a 2 on some machines (This depends on additional installed print-monitors) Quote from includes/ddk/winsplp.h: #define ROUTER_UNKNOWN 0 #define ROUTER_SUCCESS 1 #define ROUTER_STOP_ROUTING 2 /* * WARNING: Many Functions are declared as "BOOL", but return ROUTER_* */ -- By by ... Detlef

1 0

Re: [PATCH] wintrust/tests: Accept the CryptCATAdminAcquireContext win8 results
by Marvin 17 Nov '13

17 Nov '13

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=3414 Your paranoid android. === w8 (32 bit crypt) === crypt.c:554: Test failed: got 11 expected ERROR_INVALID_PARAMETER

1 0

Re: [PATCH 2/2] msxml3: Compile tests with __WINESRC__ defined.
by Marvin 16 Nov '13

16 Nov '13

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=3408 Your paranoid android. === w8 (32 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00462D8C === wxppro (32 bit domdoc) === domdoc.c:9843: Test failed: got 00244F94 === w8 (32 bit domdoc) === domdoc.c:9843: Test failed: got 002F7394

1 0

Re: [PATCH 1/2] msxml3: Return NULL instead of empty string in IXMLElement::get_tagName.
by Marvin 16 Nov '13

16 Nov '13

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=3407 Your paranoid android. === w8 (32 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00462DCC

1 0

Re: msxml3: Compile tests with __WINESRC__ defined.
by Marvin 16 Nov '13

16 Nov '13

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=3405 Your paranoid android. === wxppro (32 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00463F3D === wvista (32 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00463F3D === w2008s64 (32 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00463F3D === w7pro64 (32 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00463F3D === w8 (32 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00463F3D === w864 (32 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00463F3D === w2008s64 (64 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00000000004584D4 === w7pro64 (64 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00000000004584D4 === w864 (64 bit xmldoc) === xmldoc: unhandled exception c0000005 at 00000000004584D4 === wxppro (32 bit domdoc) === domdoc.c:9843: Test failed: got 00244F94 === w8 (32 bit domdoc) === domdoc.c:9843: Test failed: got 00301F24

1 0

Re: [PATCH] winex11: add virtual desktop mode 320x240
by Henri Verbeet 15 Nov '13

15 Nov '13

On 14 November 2013 10:25, Patrick Rudolph <siro(a)das-labor.org> wrote: > This patch adds support for display mode 320x240. Without this patch > DDraw:SetDisplayMode fails to set the virtual desktop window to 320x240. > Can you actually set 320x240 on Windows through e.g. ChangeDisplaySettingsEx()? I have the impression that this mode may be internal to ddraw.

1 0

win9x mode gone
by Damian Ivanov 15 Nov '13

15 Nov '13

Hi, In my recent installation on openSUSE 13.1 with wine 1.7.6 I can't find wine to set winver=win95 only nt based systems are available but with them my app crashes that it needs win95 Is win9x version gone in recent versions? Is it gone because of 64bit OS?

4 7

Call to action: Windows 8 tests cleanup
by Francois Gouget 15 Nov '13

15 Nov '13

There are still a lot of failing Windows 8 tests. If I only look at tests that fail on every single system we have test results for and further ignore most Direct X tests, I already get 29 tests for a total of 533 individual test failures! cmd.exe:batch (1) crypt32:sip (1) kernel32:console (56) kernel32:heap (20) kernel32:locale (62) mshtml:activex (6) ntdll:pipe (8) ole32:marshal (36) quartz:filtergraph (crash) rpcrt4:cstub (crash) shell32:ebrowser (3) shell32:shellpath (3) shell32:shlexec (13) shell32:shlfolder (1) shlwapi:assoc (1) shlwapi:ordinal (25) urlmon:misc (2) urlmon:protocol (46) urlmon:sec_mgr (20) urlmon:uri (3) urlmon:url (94) user32:cursoricon (55) user32:edit (4) user32:msg (10) user32:win (11) wininet:urlcache (17) winmm:midi (32) wintrust:crypt (2) wintrust:softpub (crash) Overall we have 47 tests that have failures on Windows versions ranging from XP to 8.1. We need a lot more tests to succeed in order for the WineTestBot to be at its best. List collected from: http://test.winehq.org/data/1f8636c5afc9aab85abed759627c1fa25e3b2131/index_… http://test.winehq.org/data/eebc40f2b3935819584a20187af2e6f782270838/index_… -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ I haven't lost my mind, it's backed up on tape around here somewhere...

1 0

WineTestBot status update
by Francois Gouget 15 Nov '13

15 Nov '13

We switched to the new WineTestBot near the start of September. Early on it ran into a problem when it was flooded with tests due to the __WINESRC__ tests work and it failed to keep up. The reason is that as time went on the time it takes to get the VMs back to a clean state ready to run the tests (the revert time) kept increasing as can be seen on this graph: http://fgouget.free.fr/wtb/vm1-revtimes.png There one can see the increased activity in september that what was caused by the surge in test patches. But the most remarkable feature is the Windows XP revert times which increase linearly, reaching over 30 minutes. The revert times for the other VMs are much more random but still seem to increase somewhat (1). The reason for the increase is still unknown. The revert time fell down a few times and now I suspect this corresponds to times when the VM was restored from backup. So at the start of October I upgraded to QEMU 1.6.0 and restored all the VMs from backup, hoping this would solve the problem. The revert times did get much better and the WineTestBot now manages to keep up: http://fgouget.free.fr/wtb/vm1-revtimes-new.png The upgrade happened around the 2nd of october and the revert times fell at that point. But looking at more recent data it's clear that the Windows XP revert times are increasing again, while those of the other VMs remain stable (see vm1-revtimes.xls for the raw data). That XP VM is one of the first ones I created, so it probably was created with a pretty old QEMU version. Futhermore it was only an out of the box SP2 and did not have any of the later updates. So I decided to recreate it from scratch, using QEMU 1.6.0, and to add all the other updates as I was at it. And I'm hoping that this time things will be better. That's why this VM is currently in 'maintenance' mode. I also took down the 32-bit Windows 8 VM for maintenance. It too is missing proper updates and the plan is to upgrade it to Windows 8.1. Another issue has been that the tests are running a bit slow, a particular point of pain was msi:action and msi:install which were regularly timing out. See: http://fgouget.free.fr/wtb/runtimes.htm So while rebuilding the Windows XP VM I did some performance tests. That paid off. I found that switching the emulated disk cache mode from writeback to default roughly halves the msi run times: http://fgouget.free.fr/wtb/runtimes2.htm msi:action and msi:install went from an average of 99 and 90 seconds down to 48 and 39 seconds and they are not timing out anymore. The remaining troublesome tests are now ddraw:ddraw{2,4,7}, shell32:shlexec, and winspool.drv:info. I also uncovered two other potential performance issues: * Some VMs have Windows Defender and apparently it was starting a full disk scan as soon as the VM was ready to run the tests. That's clearly not good so I disabled Windows Defender in all VMs. * Most VMs were still using 20% of the CPU when idle. That's fine if only one VM is running but could impact performance (through increased interrupt rates) if many are running at once (like on the WineTestBot). Apparently the culprit is the USB Tablet device that's added by default. So I removed it from all VMs too (and now the mouse is even more laggy than before when I work on the VMs :-( But that does not impact the tests). So there is still a lot of work to do on the WineTestBot, and that's not even counting fixing all the failing tests. (1) It's almost as if the increasing Windows XP revert times were pulling up the other VM revert times. Yet there's only one revert at a given time, so I don't see how this would be possible. (2) Setting the cache mode to writeback was improving the performance quite a bit with the pre-upgrade QEMU version. But obviously it's not true anymore. Another interesting point is that the Virtio mode improves performance by a factor of 10 (down from 450 seconds to 45 in msi:action). Yet Windows 8 posts the fastest times yet in the basic IDE mode (~23 seconds). I couldn't get Windows 8 working with the Virtio disk yet and I have not verified that it's really doing the same set of tests. So that remains to be confirmed. Here is some performance data taken from the Windows XP VM while the TestBot was idle. From it cache=default looks like it's a completely separate mode! msi:action | msi:install | msi:msi 448 460 520| 487 439 | 238 229 VGA, qcow2 ide disk, cache:default 44 45 42 | 47 49 46 | 24 23 21 VGA, qcow2 virtio disk, cache:default 48 45 50 | 47 48 48 | 23 23 24 VMVGA/VGA, qcow2 virtio disk, cache:default 47 46 | 48 46 | 23 22 22 VMVGA, qcow2 virtio disk, cache:default 47 47 | 49 48 | 24 23 VMVGA, raw virtio disk, cache:default 62 67 67 | 64 60 63 | 29 27 27 VMVGA, raw virtio disk, cache:none 111 92 72 113 | 101 101 | 37 37 40 VMVGA, raw virtio disk, cache:writethrough 61 64 53 | 70 59 58 | 36 28 29 VMVGA, raw virtio disk, cache:writeback 46 44 | | VMVGA, raw virtio disk, cache:default 71 55 68 | | VMVGA, raw virtio disk, cache:writeback 65 71 72 69| | VMVGA, raw virtio disk, cache:none 76 118 111 | | VMVGA, raw virtio disk, cache:writethrough 50 48 47 | | VMVGA, raw virtio disk, cache:default And the preliminary Windows 8 performance. I hope it holds up. msi:action | msi:install | msi:msi 23 22 22 | 16 15 16 | 13 13 15 VGA, qcow2 ide disk, cache:default -- Francois Gouget <fgouget(a)codeweavers.com>

6 12

Re: [PATCH] ddraw: fill dwNumFourCCCodes in ddraw7_GetCaps
by Henri Verbeet 14 Nov '13

14 Nov '13

On 14 November 2013 17:17, Patrick Rudolph <siro(a)das-labor.org> wrote: > hr = IDirectDraw7_GetAvailableVidMem(iface, &ddscaps, &caps.dwVidMemTotal, &caps.dwVidMemFree); > - wined3d_mutex_unlock(); > if(FAILED(hr)) { > WARN("IDirectDraw7::GetAvailableVidMem failed\n"); > return hr; > } You now fail to release the mutex on the error path. Wrt. style, I realize ddraw isn't entirely consistent about this, but you'll want to put a space between the "if" and the '(', and but the '{' on a new line.

1 0

Re: shell32/tests: add a missed init_shfo_tests() call
by Marvin 13 Nov '13

13 Nov '13

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=3354 Your paranoid android. === build (build) === Patch failed to apply

1 0

Potential miss usage of strchr VS strrchr in Wine (was: [PATCH] wscript: Get extension name by strrchrW instead of strchrW.)
by Qian Hong 13 Nov '13

13 Nov '13

Hello, While working on a vbscript bug affects a real world app, I found a potential miss usage of strchr/strrch in Wine. Here is a unfiltered list: $ git grep "= strchr" | grep ext | grep -E "'\.'" dlls/gdi32/freetype.c: ext = strchr( last_part, '.' ); dlls/msi/action.c: extension = strchrW( filename, '.' ); dlls/wineps.drv/type1afm.c: CHAR *file_extension = strchr(dent->d_name, '.'); tools/winebuild/utils.c: if (!(ext = strchr( basename, '.' ))) ext = prefix + strlen(prefix); After basic reviewing, I think all the above codes are potential miss usage, but there is a risk to touch these codes. I don't know any real word app affected by these codes yet, so I have no strong motivation to touch them. Anyone worked on related fields has interesting to review deeper? Thanks! On Tue, Nov 12, 2013 at 4:19 PM, Qian Hong <qhong(a)codeweavers.com> wrote: > --- > programs/wscript/main.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > -- Regards, Qian Hong - http://www.codeweavers.com

2 1

Re: user32/tests: Allow win8 error code
by Marvin 13 Nov '13

13 Nov '13

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=3343 Your paranoid android. === w8 (32 bit sysparams) === sysparams.c:2488: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2501: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1 === w864 (32 bit sysparams) === sysparams.c:2488: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2501: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

1 0

WINE CE - getting a program to execute
by Mark Bellmore 12 Nov '13

12 Nov '13

Hello, I have some winCE apps they would like to run on Android. Since WINE for Android will not be out for several months I thought I would investigate how to get applications running under the winece that is currently available. I successfully installed it on a pandaboard and the demo applications that come with the install work (e.g. clock.exe). I downloaded what I thought was a typical application that did not have any additional dlls (putty.exe) but it immediately returns with: wine: Invalid address I am a fairly competent c programmer but I was hoping I could get some pointers on where to get started since there is a lot of codebase to wade through. If you think it cannot be done by a newbie please don't hesitate to say so :) Thanks! = Mark ----------------------- Here is the results from windump putty.exe File Header Machine: 01C0 (ARM) Number of Sections: 5 TimeDateStamp: 45E5F329 (Wed Feb 28 15:24:57 2007) offset 216 PointerToSymbolTable: 00000000 NumberOfSymbols: 00000000 SizeOfOptionalHeader: 00E0 Characteristics: 010F RELOCS_STRIPPED EXECUTABLE_IMAGE LINE_NUMS_STRIPPED LOCAL_SYMS_STRIPPED 32BIT_MACHINE Optional Header (32bit) Magic 0x10B 267 linker version 6.24 size of code 0x53c00 343040 size of initialized data 0x1f200 127488 size of uninitialized data 0x0 0 entrypoint RVA 0x5499c 346524 base of code 0x1000 4096 base of data 0x55000 348160 image base 0x10000 65536 section align 0x1000 4096 file align 0x200 512 required OS version 4.00 image version 0.00 subsystem version 4.20 Win32 Version 0x0 0 size of image 0x75000 479232 size of headers 0x400 1024 checksum 0x0 0 Subsystem 0x9 (Windows CE GUI) DLL characteristics: 0x0 stack reserve size 0x10000 65536 stack commit size 0x1000 4096 heap reserve size 0x100000 1048576 heap commit size 0x1000 4096 loader flags 0x0 0 RVAs & sizes 0x10 16 Data Directory EXPORT rva: 0x0 size: 0x0 IMPORT rva: 0x62258 size: 0x28 RESOURCE rva: 0x73000 size: 0x1f4c EXCEPTION rva: 0x71000 size: 0x1e90 SECURITY rva: 0x0 size: 0x0 BASERELOC rva: 0x0 size: 0x0 DEBUG rva: 0x0 size: 0x0 ARCHITECTURE rva: 0x0 size: 0x0 GLOBALPTR rva: 0x0 size: 0x0 TLS rva: 0x0 size: 0x0 LOAD_CONFIG rva: 0x0 size: 0x0 Bound IAT rva: 0x0 size: 0x0 IAT rva: 0x63000 size: 0x368 Delay IAT rva: 0x0 size: 0x0 CLR Header rva: 0x0 size: 0x0 rva: 0x0 size: 0x0 ----------------- Here is the last several lines from setting WINDEDEBUG=+all 0030: open_key( parent=0010, access=000f003f, attributes=00000000, name=L"Software\\Wine\\DllOverrides" ) 0030: open_key() = OBJECT_NAME_NOT_FOUND { hkey=0000 } 0030: close_handle( handle=0010 ) 0030: close_handle() = 0 0030: get_handle_fd( handle=000c ) 0030: *fd* 000c -> 21 0030: get_handle_fd() = 0 { type=1, cacheable=1, access=00120089, options=00000000 } 0030: create_mapping( access=000f0005, attributes=00000000, protect=00000145, size=00000000, file_handle=000c, objattr={rootdir=0000,sd={},name=L""} ) 0030: create_mapping() = 0 { handle=0010 } 0030: get_mapping_info( handle=0010, access=00000004 ) 0030: get_mapping_info() = 0 { size=00075000, protect=325, header_size=1024, base=00010000, mapping=0014, shared_file=0000 } 0030: get_handle_fd( handle=0010 ) 0030: *fd* 0010 -> 22 0030: get_handle_fd() = 0 { type=1, cacheable=1, access=000f0005, options=00000020 } 0030: close_handle( handle=0014 ) 0030: close_handle() = 0 0030: close_handle( handle=0010 ) 0030: close_handle() = 0 0030: close_handle( handle=000c ) 0030: close_handle() = 0 0030: terminate_process( handle=0000, exit_code=487 ) 0030: terminate_process() = 0 { self=1 } 0030: terminate_process( handle=ffffffff, exit_code=487 ) 0030: terminate_process() = 0 { self=1 } 0030: *killed* exit_code=487 002f: *process killed*

2 1

Re: [PATCH 3/3] ws2_32: Add an interactive test for interface change notifications (rebased).
by Marvin 12 Nov '13

12 Nov '13

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=3330 Your paranoid android. === wxppro (32 bit sock) === sock.c:520: Test failed: oob_server (470): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:510: Test failed: oob_server (7a4): unexpectedly at the OOB mark: 0 sock.c:520: Test failed: oob_server (7a4): unexpectedly at the OOB mark: 0 sock: unhandled exception c0000005 at 757C9799 === w2008s64 (64 bit sock) === sock.c:520: Test failed: oob_server (704): unexpectedly at the OOB mark: 0 === w864 (64 bit sock) === sock.c:1748: Test failed: getservbyname: winsock resized servent buffer when not necessary

1 0

Re: [PATCH 1/5] d3d8: Clear pBits and Pitch when d3d8_surface_LockRect() fails.
by Marvin 12 Nov '13

12 Nov '13

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=3328 Your paranoid android. === w8 (32 bit device) === device.c:2494: Test failed: Expected foreground window 00030196, got 0002004E. device.c:3190: Test failed: Expected wndproc 0x40fff0, got 0x40fff0. === w864 (32 bit device) === device.c:2494: Test failed: Expected foreground window 0004017A, got 0001007A. device.c:3190: Test failed: Expected wndproc 0x40fff0, got 0x40fff0.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel