- wine-devel - winehq.org

Regarding DXVA support in Wine (DXVA2 -> VA_API)
by Jaeyong Yoo 30 Jul '14

30 Jul '14

Hello Wine, I've seen Michael Muller is writing DXVA2 -> VA_API conversion in the following link:

1 0

Re: mshtml: Added IHTMLInputElement_get_form method implementation. (try 2)
by Jacek Caban 29 Jul '14

29 Jul '14

Hi Zhenbo, On 07/29/14 05:24, Zhenbo Li wrote: > + nsres = nsIDOMHTMLInputElement_GetForm(This->nsinput, &nsform); > + if (NS_FAILED(nsres) || nsform == NULL) { > + ERR("GetForm failed: %08x, nsform: %p\n", nsres, nsform); > + p = NULL; Not setting output value would be probably fine in this case, but if you do, please do it right (*p = NULL;). Jacek

1 0

Re: mshtml: Added IHTMLWindow2::navigate implementation.
by Marvin 28 Jul '14

28 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8129 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [3/3] wined3d: replace vendor specific callbacks with generic code that uses vendor specific renderer string tables
by Henri Verbeet 28 Jul '14

28 Jul '14

On 26 July 2014 20:24, Andrei Slăvoiu <andrei.slavoiu(a)gmail.com> wrote: > + /*Direct 3D 11*/ I guess this happened while rebasing.

2 1

Re: XInput over SDL
by akjsdfk sdkfnskd 28 Jul '14

28 Jul '14

> My 2c is that this is more of an issue than SDL. Using SDL is probably > fine if there are good arguments that support its use and the > Wine-internal layering makes sure that xinput_*.dll, dinput > and winmm see the same joystick configuration. You could think about > calling SDL from winex11.drv or dinput. I think you missed the point completely here. Example I posted link for is not if you see/can use device or you don't as device is visible full time. Games use this code to decide which interface they use that way to run, DInput or XInput. And since that code does following - enumerate all DInput visible devices (XInput are exposed there too) ---- for each DInput device check if it is XInput ------ for each passed DInput device parse trough all system devices and when you find it (!!!!!) -------- check if device ID contains "IG_", if it does lets proclaim this XInput compatible now if any of devices was XInput compatible LoadLibrary ("XInput1_3.dll") and use XInput API, if there was no compatible device then LoadLibrary ("DInput.dll") and use DInput API. This all happens in game, not in Windows or Wine. In wine case, NO compatible device is reported (!!!!!) - This part is where my question was aiming for, which part of wine creates devices here, so I wouldn't need to hack CoSetProxyBlanket This part has nothing to do with DInput or XInput. Wine simply doesn't provide XInput compatible device when game parses them with CoSetProxyBlanket setup enumeration Maybe you missed it before "*If you want your game to support legacy DirectInput <http://msdn.microsoft.com/en-us/library/windows/desktop/ee416842(v=vs.85).a…>** devices, you may use DirectInput and XInput side by side. When enumerating your DirectInput devices, all DirectInput devices will enumerate correctly. All XInput devices will show up as both XInput and DirectInput devices, but they should not be handled through DirectInput. You will need to determine which of your DirectInput devices are legacy devices, and which are XInput devices, and remove them from the enumeration of DirectInput devices.*" >From same page > I guess here you mean the X input extension rather than Microsoft's > xinput_*.dll, right? I guess XInput works better in remote X11 > situations than anything SDL, /dev/js* or /dev/event/* based. (But tbh I > don't really know how SDL talks to the joystick.) No, I meant exactly what I said. XInput is terribly deficient API. And as far as remote situations, X11 has way too terrible remote display to be usable for game in 50x50 resolution, way off some normal @Vincent Povirk > From what I could tell, SDL has a game controller api that's very > similar to xinput, which is pretty nice, and it can be configured to > map to any controller. It goes further, you can access same device as Joystick and handle axis and buttons manually or you can access it as Gamepad and have instant correct axis/button mapping. Not to mention haptic in XInput is downright terribly deficient (set left/right, ok it works), SDL is downright brilliant on haptic handling Since I'm not native english speaker, some parts might sound like I would try to persuade in use of SDL. If it does, I sincerely apologize and believe me... I don't, I'm honestly only interested in my question regarding who/where creates devices in CoSetProxyBlanket part p.s. sorry for double message Stefan, accidentally only sent response to you and not to list with regards wh1sper_123 On 28 July 2014 20:43, akjsdfk sdkfnskd <wh1sper.123.wtfit(a)gmail.com> wrote: > > My 2c is that this is more of an issue than SDL. Using SDL is probably > > fine if there are good arguments that support its use and the > > Wine-internal layering makes sure that xinput_*.dll, dinput > > and winmm see the same joystick configuration. You could think about > > calling SDL from winex11.drv or dinput. > > I think you missed the point completely here. > > Example I posted link for is not if you see/can use device or you don't as > device is visible full time. Games use this code to decide which interface > they use that way to run, DInput or XInput. And since that code does > following > - enumerate all DInput visible devices (XInput are exposed there too) > ---- for each DInput device check if it is XInput > ------ for each passed DInput device parse trough all system devices and > when you find it (!!!!!) > -------- check if device ID contains "IG_", if it does lets proclaim this > XInput compatible > > now if any of devices was XInput compatible LoadLibrary ("XInput1_3.dll") > and use XInput API, if there was no compatible device then LoadLibrary > ("DInput.dll") and use DInput API. This all happens in game, not in Windows > or Wine. In wine case, NO compatible device is reported > > (!!!!!) - This part is where my question was aiming for, which part of > wine creates devices here, so I wouldn't need to hack CoSetProxyBlanket > > This part has nothing to do with DInput or XInput. Wine simply doesn't > provide XInput compatible device when game parses them with CoSetProxyBlanket > setup enumeration > > Maybe you missed it before "*If you want your game to support > legacy DirectInput > <http://msdn.microsoft.com/en-us/library/windows/desktop/ee416842(v=vs.85).a…>** devices, > you may use DirectInput and XInput side by side. When enumerating your > DirectInput devices, all DirectInput devices will enumerate correctly. All > XInput devices will show up as both XInput and DirectInput devices, but > they should not be handled through DirectInput. You will need to determine > which of your DirectInput devices are legacy devices, and which are XInput > devices, and remove them from the enumeration of DirectInput devices.*" > From same page > > > I guess here you mean the X input extension rather than Microsoft's > > xinput_*.dll, right? I guess XInput works better in remote X11 > > situations than anything SDL, /dev/js* or /dev/event/* based. (But tbh I > > don't really know how SDL talks to the joystick.) > > No, I meant exactly what I said. XInput is terribly deficient API. And as > far as remote situations, X11 has way too terrible remote display to be > usable for game in 50x50 resolution, way off some normal > @Vincent Povirk > > From what I could tell, SDL has a game controller api that's very > > similar to xinput, which is pretty nice, and it can be configured to > > map to any controller. > > It goes further, you can access same device as Joystick and handle axis > and buttons manually or you can access it as Gamepad and have instant > correct axis/button mapping. Not to mention haptic in XInput is downright > terribly deficient (set left/right, ok it works), SDL is downright > brilliant on haptic handling > > > Since I'm not native english speaker, some parts might sound like I would > try to persuade in use of SDL. If it does, I sincerely apologize and > believe me... I don't, I'm honestly only interested in my question > regarding who/where creates devices in CoSetProxyBlanket part > > with regards > wh1sper_123 > > > On 28 July 2014 19:50, Stefan Dösinger <stefandoesinger(a)gmail.com> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Am 2014-07-26 22:52, schrieb akjsdfk sdkfnskd: >> > - hotplugging/unplugging (well, only if game didn't use DInput to >> > scan new devices. if it is pure XInput, then it just works) >> My 2c is that this is more of an issue than SDL. Using SDL is probably >> fine if there are good arguments that support its use and the >> Wine-internal layering makes sure that xinput_*.dll, dinput >> and winmm see the same joystick configuration. You could think about >> calling SDL from winex11.drv or dinput. >> >> > - far better API than XInput >> I guess here you mean the X input extension rather than Microsoft's >> xinput_*.dll, right? I guess XInput works better in remote X11 >> situations than anything SDL, /dev/js* or /dev/event/* based. (But tbh I >> don't really know how SDL talks to the joystick.) >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2 >> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >> >> iQIcBAEBAgAGBQJT1o1zAAoJEN0/YqbEcdMwWiYP/1/hOzt/v6VIp+gDS+cYJF5u >> 4fRyjT4zoWoFmOUrtApSj1VaBA2DeIaeeT97D0AAvD+FQ0GLaSYcEbn2EqLTcPJO >> N2IGHeTABdt3IBcD1Ya4AOVAryITaqoR83qmI6KElv/jrdpNDD6BaMemcFDno4Tm >> pqAYdlZBlFUWP5kEcSp7OsztNWCin0gdQ6BRRnU8nhtBtlOC5qV9VQPW5CQ66SDK >> +CM+3YkzARMoqmPk1qNu/OnkrubRRuwpHLsCySkfE9WnIDd29tIEAvMThUeZ8ucN >> OKmdIhs+RSOijrZecj0QDzhNA3fPR+EYx+OFr6h10Y3PxOgdwwAstDoakEhk1x4Y >> /jQu0XKtP6hDqCtSruxE8Ny3Hpb8p/zsdodHIhmp1W99QdHLbnKVdZJiCYBLToFW >> AVJ69NPm4Ae92jerN8pesHEl5B7kIGkQepCCpxWUjwPVWEjbB6fEcegGcGN/ccNn >> EWiBm1+14L5wgPSPCG/DhAfEPtfsig7TLdsL6zIZFLq0/+O6PVmjW9ezjT1PD00U >> NP7VqmYWY5Is7XtWI6NQ1Vqi5En47uKz+ZaQLPB0ExQB57XrubMo6C6aE53Q4HRg >> 5Kmh7vTBZecXPZGToT6Eg3z3y1Bc6B9piipxxfRzuqOU6EUzqHO8RzG/LuMrOLG7 >> kHdS1Q1gRro1FRAFDT3M >> =gcqc >> -----END PGP SIGNATURE----- >> > >

1 0

Re: mshtml: Added IHTMLInputElement_get_form method implementation.
by Jacek Caban 28 Jul '14

28 Jul '14

On 07/28/14 16:58, Zhenbo Li wrote: > My code is a little ugly, and I'm wondering if there is a better > solution. Is there any reason why you don't use nsIDOMHTMLInputElement::GetForm? Jacek

1 0

Re: [PATCH 4/4] vbscript: Implemented ScriptEngineMinorVersion(try 2)
by Marvin 28 Jul '14

28 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8122 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [PATCH 3/4] vbscript: Implemented ScriptEngineMajorVersion(try 2)
by Marvin 28 Jul '14

28 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8121 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [PATCH 2/4] vbscript: Inplemented ScriptEngineBuildVersion(try 2)
by Marvin 28 Jul '14

28 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8120 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [PATCH 1/4] vbscript: Implemented ScriptEngine(try 2)
by Marvin 28 Jul '14

28 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8119 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [PATCH 4/4] vbscript: Implemented ScriptEngineMinorVersion
by Marvin 28 Jul '14

28 Jul '14

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

1 0

Re: [PATCH 3/4] vbscript: Implemented ScriptEngineMajorVersion
by Marvin 28 Jul '14

28 Jul '14

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

1 0

Re: [PATCH 2/4] vbscript: Implemented ScriptEngineBuildVersion
by Marvin 28 Jul '14

28 Jul '14

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

1 0

Re: [PATCH 1/4] vbscript: Implemented ScriptEngine
by Marvin 28 Jul '14

28 Jul '14

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

1 0

Partial fix for issue 17982 (PatBlt cannot draw arbitrary parallelograms based on the world transform)
by Alexander Almaleh 28 Jul '14

28 Jul '14

I made a partial fix of this bug - https://bugs.winehq.org/show_bug.cgi?id=17982, only for the PATCOPY rop. It's based on the observation that the Polygon() function does support arbitrary parallelograms, including when defined through the XFORM matrix, so for PATCOPY we can just delegate the implementation to it (with a NULL_PEN because PatBlt doesn't use a pen). Is this patch acceptable? I have no idea if delegating to Polygon() will hurt performance. If that is a concern, I can do it only in case the physical coordinates after the world transform are not rectangular. If it is, I will submit it to wine-patches, then.

1 0

dlls/ntdll/signal_i386.c changes break FreeBSD
by Gerald Pfeifer 25 Jul '14

25 Jul '14

Over the last 24 hours, signal_i386.c stopped building on FreeBSD/i386 10.0 as follows: +signal_i386.c:283:40: error: 'ucontext_t' has no member named 'sc_trapno' +signal_i386.c:284:40: error: 'ucontext_t' has no member named 'sc_err' +signal_i386.c:279:40: error: 'ucontext_t' has no member named 'sc_fs' +signal_i386.c:280:40: error: 'ucontext_t' has no member named 'sc_gs' +signal_i386.c:276:40: error: 'ucontext_t' has no member named 'sc_cs' +signal_i386.c:281:40: error: 'ucontext_t' has no member named 'sc_ss' +signal_i386.c:288:40: error: 'ucontext_t' has no member named 'sc_esp' +signal_i386.c:268:40: error: 'ucontext_t' has no member named 'sc_eax' +signal_i386.c:269:40: error: 'ucontext_t' has no member named 'sc_ebx' +signal_i386.c:270:40: error: 'ucontext_t' has no member named 'sc_ecx' +signal_i386.c:271:40: error: 'ucontext_t' has no member named 'sc_edx' +signal_i386.c:272:40: error: 'ucontext_t' has no member named 'sc_esi' +signal_i386.c:273:40: error: 'ucontext_t' has no member named 'sc_edi' : +signal_i386.c:997:1: warning: control reaches end of non-void function [-Wreturn-type] +signal_i386.c:566:1: warning: control reaches end of non-void function [-Wreturn-type] +signal_i386.c:580:1: warning: control reaches end of non-void function [-Wreturn-type] On FreeBSD, /usr/include/sys/ucontext.h has the following: typedef struct __ucontext { /* * Keep the order of the first two fields. Also, * keep them the first two fields in the structure. * This way we can have a union with struct * sigcontext and ucontext_t. This allows us to * support them both at the same time. * note: the union is not defined, though. */ sigset_t uc_sigmask; mcontext_t uc_mcontext; struct __ucontext *uc_link; stack_t uc_stack; int uc_flags; #define UCF_SWAPPED 0x00000001 /* Used by swapcontext(3). */ int __spare__[4]; } ucontext_t; mcontext_t is defined in /usr/include/x86/ucontext as follows: typedef struct __mcontext { /* * The definition of mcontext_t must match the layout of * struct sigcontext after the sc_mask member. This is so * that we can support sigcontext and ucontext_t at the same * time. */ __register_t mc_onstack; /* XXX - sigcontext compat. */ __register_t mc_gs; /* machine state (struct trapframe) */ __register_t mc_fs; __register_t mc_es; __register_t mc_ds; __register_t mc_edi; __register_t mc_esi; __register_t mc_ebp; __register_t mc_isp; __register_t mc_ebx; __register_t mc_edx; __register_t mc_ecx; __register_t mc_eax; __register_t mc_trapno; __register_t mc_err; __register_t mc_eip; __register_t mc_cs; __register_t mc_eflags; __register_t mc_esp; __register_t mc_ss; : Gerald

2 2

Re: [1/3] oleaut32: Add test for TLB dependencies lookup in resources (try 2)
by Guillaume Charifi 25 Jul '14

25 Jul '14

Alexandre Julliard wrotes: > Simply create it directly into a temp dir, no moving needed. I am reusing a TLB created by building process, because this test requires two typelibs, to check whether or not, from a TypeInfo requested from one of them, we can get the corresponding RefTypeInfo from the other. The aim is to see if the imlementation can find the TypeLib in which the RefTypeInfo is. So I don't really need to create it at runtime, I just need it to be in the ressource table of the test program, and nowhere else.

1 0

Re: [1/3] oleaut32: Add test for TLB dependencies lookup in resources (try 2)
by Guillaume Charifi 25 Jul '14

25 Jul '14

Alexandre Julliard wrotes: > Simply create it directly into a temp dir, no moving needed. I am reusing a TLB created by building process, because this test requires two typelibs, to check whether or not, from a TypeInfo requested from one of them, we can get the corresponding RefTypeInfo from the other. The aim is to see if the imlementation can find the TypeLib in which the RefTypeInfo is. So I don't really need to create it at runtime, I just need it to be in the ressource table of the test program, and nowhere else.

1 0

Re: [1/3] oleaut32: Add test for TLB dependencies lookup in resources (try 2)
by Guillaume Charifi 25 Jul '14

25 Jul '14

Alexandre Julliard <julliard at winehq.org> writes: > It doesn't work here: > > ../../../tools/runtest -q -P wine -T ../../.. -M oleaut32.dll -p oleaut32_test.exe.so typelib && touch typelib.ok > typelib.c:5528: Test failed: test_tlb.tlb is on the path or registered > typelib.c:5542: Test succeeded inside todo block: got: 0 > make[1]: *** [typelib.ok] Error 2 Yes, in fact the test does not make sense if the test_tlb.tlb is locatable on disk by the program, it must be out of the path. That's why I was initially just skipping the test if test_tlb.tlb could be loaded from disk, but some suggested me to make the test fail in that case. Should I restore the old behaviour ? Or do something else ?

2 2

Re: [1/3] oleaut32: Add test for TLB dependencies lookup in resources (try 2)
by Alexandre Julliard 24 Jul '14

24 Jul '14

Guillaume Charifi <guillaume.charifi(a)sfr.fr> writes: > Some file had nothing to be there... > > Supersedes http://source.winehq.org/patches/data/105527 > --- > dlls/oleaut32/tests/Makefile.in 1 + > dlls/oleaut32/tests/test_dep.idl 44 > ++++++++++++++++++++++++++++++++++++++++++++ > dlls/oleaut32/tests/tmarshal.rc 3 +++ > dlls/oleaut32/tests/typelib.c 40 > ++++++++++++++++++++++++++++++++++++++++ > 4 files changed, 88 insertions(+) It doesn't work here: ../../../tools/runtest -q -P wine -T ../../.. -M oleaut32.dll -p oleaut32_test.exe.so typelib && touch typelib.ok typelib.c:5528: Test failed: test_tlb.tlb is on the path or registered typelib.c:5542: Test succeeded inside todo block: got: 0 make[1]: *** [typelib.ok] Error 2 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: libwine: Added wine_dbgstr_variant and wine_dbgstr_vt implementations.
by Alexandre Julliard 24 Jul '14

24 Jul '14

Jacek Caban <jacek(a)codeweavers.com> writes: > This is meant to remove all the duplicated debugstr_variant > implementations. While this is ugly, mostly due to duplicated > declarations, this is the most straightforward solution. An alternative > would be to implement this in ntdll (using __wine_debug_functions). This > would avoid headers problem (well, it's still ugly to use oaidl.h in > ntdll, but technically allowed) and allow exception protection, like > string printing functions. I'm not sure if that's better. I'm ready to > change the patch. Either way requires breaking the libwine interface, it's not worth it for something like that. Simply make them inline in debug.h. We don't want to include the needed headers from debug.h, but you could make the definitions conditional on the headers having been already included. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: urlmon: Don't threat '#' as path delimiter in file URIs.
by Marvin 24 Jul '14

24 Jul '14

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

1 0

Re: wine.inf: Create Links directory in user profile folder to make SHGetKnownFolderPath working for KNOWNFOLDERID_Links (with test)
by Alexandre Julliard 24 Jul '14

24 Jul '14

Stefan Leichter <Stefan.Leichter(a)camline.com> writes: > @@ -2552,6 +2552,7 @@ HKLM,%CurrentVersion%\Telephony\Country List\998,"SameAreaRule",,"G" > 16410,Microsoft, > 16412,Microsoft, > 16422,Internet Explorer,iexplore.exe > +16424,Links, It should be created in shell32 like the other shell folders. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 1/4] msi: Don't publish features with non positive install level
by Marvin 24 Jul '14

24 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8087 Your paranoid android. === w2000pro (32 bit package) === package.c:3985: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:3991: Test failed: Expected "C:\\FileName2", got "C:\FileName2" package.c:3997: Test failed: Expected "C:\\FileName3", got "C:\FileName3" package.c:4009: Test failed: Expected "C:\\FileName5", got "C:\FileName5" package.c:4015: Test failed: Expected "C:\\", got "C:\" package.c:4021: Test failed: Expected "C:\\", got "C:\" package.c:4037: Test failed: Expected "C:\\FileName8.dll", got "C:\FileName8.dll" package.c:4048: Test failed: Expected "C:\\FileName10.dll", got "C:\FileName10.dll" package.c:4507: Test failed: Expected ERROR_SUCCESS, got 1627 package.c:4599: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:4610: Test failed: Expected "C:\\", got "C:\" package.c:4621: Test failed: Expected "C:\\", got "C:\" package.c:4671: Test failed: Expected "C:\\FileName3.dll", got "C:\FileName3.dll" package.c:4682: Test failed: Expected "C:\\FileName5.dll", got "C:\FileName5.dll" package.c:4697: Test failed: Expected "C:\\", got "C:\" package.c:4702: Test failed: Expected "", got "C:\" package.c:4718: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:4727: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:4977: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:4988: Test failed: Expected "C:\\", got "C:\" package.c:4994: Test failed: Expected "C:\\", got "C:\" package.c:5015: Test failed: Expected "C:\\FileName2.dll", got "C:\FileName2.dll" package.c:5026: Test failed: Expected "C:\\FileName4.dll", got "C:\FileName4.dll" package.c:5266: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:5272: Test failed: Expected "C:\\", got "C:\" package.c:5289: Test failed: Expected "C:\\one\two\three\FileName2", got "C:\one\two\three\FileName2" package.c:5300: Test failed: Expected "C:\\one\two\three\FileName2", got "C:\one\two\three\FileName2" package.c:5308: Test failed: Expected "C:\\FileName3.dll", got "C:\FileName3.dll" package.c:5652: Test failed: Expected C:\\winetest-package.msi, got C:\winetest-package.msi package.c:6284: Test failed: Expected C:\\abelisaurus or empty string, got C:\abelisaurus package.c:6308: Test failed: Expected C:\\ or empty string, got C:\ package.c:6352: Test failed: Expected C:\\ or empty string, got C:\ package.c:6361: Test failed: Expected C:\\neosodon\ or empty string, got C:\neosodon\ package.c:6591: Test failed: Expected "C:\\", got "C:\" package.c:6592: Test failed: Expected 4, got 3 package.c:6599: Test failed: Expected "C:\\", got "C:\" package.c:6600: Test failed: Expected 4, got 3 package.c:6616: Test failed: Expected "C:\\", got "C:\" package.c:6617: Test failed: Expected 4, got 3 package.c:6623: Test failed: Expected "C:\\", got "C:\" package.c:6624: Test failed: Expected 4, got 3 package.c:6631: Test failed: Expected "C:\\subsource\", got "C:\subsource\" package.c:6632: Test failed: Expected 14, got 13 package.c:6639: Test failed: Expected "C:\\subsource\sub2\", got "C:\subsource\sub2\" package.c:6640: Test failed: Expected 19, got 18 package.c:6650: Test failed: Expected "C:\\", got "C:\" package.c:6651: Test failed: Expected 4, got 3 package.c:6658: Test failed: Expected "C:\\", got "C:\" package.c:6659: Test failed: Expected 4, got 3 package.c:6675: Test failed: Expected "C:\\", got "C:\" package.c:6676: Test failed: Expected 4, got 3 package.c:6682: Test failed: Expected "C:\\", got "C:\" package.c:6683: Test failed: Expected 4, got 3 package.c:6690: Test failed: Expected "C:\\subsource\", got "C:\subsource\" package.c:6691: Test failed: Expected 14, got 13 package.c:6698: Test failed: Expected "C:\\subsource\sub2\", got "C:\subsource\sub2\" package.c:6699: Test failed: Expected 19, got 18 package.c:6709: Test failed: Expected "C:\\", got "C:\" package.c:6710: Test failed: Expected 4, got 3 package.c:6717: Test failed: Expected "C:\\", got "C:\" package.c:6718: Test failed: Expected 4, got 3 package.c:6734: Test failed: Expected "C:\\", got "C:\" package.c:6735: Test failed: Expected 4, got 3 package.c:6741: Test failed: Expected "C:\\", got "C:\" package.c:6742: Test failed: Expected 4, got 3 package.c:6749: Test failed: Expected "C:\\subsource\", got "C:\subsource\" package.c:6750: Test failed: Expected 14, got 13 package.c:6757: Test failed: Expected "C:\\subsource\sub2\", got "C:\subsource\sub2\" package.c:6758: Test failed: Expected 19, got 18 package.c:6768: Test failed: Expected "C:\\", got "C:\" package.c:6769: Test failed: Expected 4, got 3 package.c:6776: Test failed: Expected "C:\\", got "C:\" package.c:6777: Test failed: Expected 4, got 3 package.c:6793: Test failed: Expected "C:\\", got "C:\" package.c:6794: Test failed: Expected 4, got 3 package.c:6800: Test failed: Expected "C:\\", got "C:\" package.c:6801: Test failed: Expected 4, got 3 package.c:6808: Test failed: Expected "C:\\subsource\", got "C:\subsource\" package.c:6809: Test failed: Expected 14, got 13 package.c:6816: Test failed: Expected "C:\\subsource\sub2\", got "C:\subsource\sub2\" package.c:6817: Test failed: Expected 19, got 18 package.c:6832: Test failed: Expected 4, got 3 package.c:6849: Test failed: Expected 4, got 3 package.c:6855: Test failed: Expected ERROR_MORE_DATA, got 0 package.c:6858: Test failed: Expected 4, got 3 package.c:6865: Test failed: Expected "C:\\", got "C:\" package.c:6866: Test failed: Expected 4, got 3 package.c:6877: Test failed: Expected "C:\\", got "C:\" package.c:6878: Test failed: Expected 4, got 3 package.c:6973: Test failed: Expected "C:\\", got "C:\" package.c:6974: Test failed: Expected 4, got 3 package.c:6981: Test failed: Expected "C:\\", got "C:\" package.c:6982: Test failed: Expected 4, got 3 package.c:6991: Test failed: Expected "C:\\", got "C:\" package.c:6992: Test failed: Expected 4, got 3 package.c:7000: Test failed: Expected "C:\\", got "C:\" package.c:7001: Test failed: Expected 4, got 3 package.c:7007: Test failed: Expected "C:\\", got "C:\" package.c:7008: Test failed: Expected 4, got 3 package.c:7015: Test failed: Expected "C:\\", got "C:\" package.c:7016: Test failed: Expected 4, got 3 package.c:7023: Test failed: Expected "C:\\", got "C:\" package.c:7024: Test failed: Expected 4, got 3 package.c:7034: Test failed: Expected "C:\\", got "C:\" package.c:7035: Test failed: Expected 4, got 3 package.c:7042: Test failed: Expected "C:\\", got "C:\" package.c:7043: Test failed: Expected 4, got 3 package.c:7052: Test failed: Expected "C:\\", got "C:\" package.c:7053: Test failed: Expected 4, got 3 package.c:7061: Test failed: Expected "C:\\", got "C:\" package.c:7062: Test failed: Expected 4, got 3 package.c:7068: Test failed: Expected "C:\\", got "C:\" package.c:7069: Test failed: Expected 4, got 3 package.c:7076: Test failed: Expected "C:\\", got "C:\" package.c:7077: Test failed: Expected 4, got 3 package.c:7084: Test failed: Expected "C:\\", got "C:\" package.c:7085: Test failed: Expected 4, got 3 package.c:7095: Test failed: Expected "C:\\", got "C:\" package.c:7096: Test failed: Expected 4, got 3 package.c:7103: Test failed: Expected "C:\\", got "C:\" package.c:7104: Test failed: Expected 4, got 3 package.c:7113: Test failed: Expected "C:\\", got "C:\" package.c:7114: Test failed: Expected 4, got 3 package.c:7122: Test failed: Expected "C:\\", got "C:\" package.c:7123: Test failed: Expected 4, got 3 package.c:7129: Test failed: Expected "C:\\", got "C:\" package.c:7130: Test failed: Expected 4, got 3 package.c:7137: Test failed: Expected "C:\\", got "C:\" package.c:7138: Test failed: Expected 4, got 3 package.c:7145: Test failed: Expected "C:\\", got "C:\" package.c:7146: Test failed: Expected 4, got 3 package.c:7156: Test failed: Expected "C:\\", got "C:\" package.c:7157: Test failed: Expected 4, got 3 package.c:7164: Test failed: Expected "C:\\", got "C:\" package.c:7165: Test failed: Expected 4, got 3 package.c:7174: Test failed: Expected "C:\\", got "C:\" package.c:7175: Test failed: Expected 4, got 3 package.c:7183: Test failed: Expected "C:\\", got "C:\" package.c:7184: Test failed: Expected 4, got 3 package.c:7190: Test failed: Expected "C:\\", got "C:\" package.c:7191: Test failed: Expected 4, got 3 package.c:7198: Test failed: Expected "C:\\", got "C:\" package.c:7199: Test failed: Expected 4, got 3 package.c:7206: Test failed: Expected "C:\\", got "C:\" package.c:7207: Test failed: Expected 4, got 3 package.c:7304: Test failed: Expected "C:\\long\", got "C:\long\" package.c:7305: Test failed: Expected 9, got 8 package.c:7314: Test failed: Expected "C:\\long\", got "C:\long\" package.c:7315: Test failed: Expected 9, got 8 package.c:7324: Test failed: Expected "C:\\long\", got "C:\long\" package.c:7325: Test failed: Expected 9, got 8 package.c:7336: Test failed: Expected "C:\\two\", got "C:\two\" package.c:7337: Test failed: Expected 8, got 7 package.c:7348: Test failed: Expected "C:\\four\", got "C:\four\" package.c:7349: Test failed: Expected 9, got 8 package.c:7360: Test failed: Expected "C:\\six\", got "C:\six\" package.c:7361: Test failed: Expected 8, got 7 package.c:7372: Test failed: Expected "C:\\eight\", got "C:\eight\" package.c:7373: Test failed: Expected 10, got 9 package.c:7384: Test failed: Expected "C:\\ten\", got "C:\ten\" package.c:7385: Test failed: Expected 8, got 7 package.c:7396: Test failed: Expected "C:\\twelve\", got "C:\twelve\" package.c:7397: Test failed: Expected 11, got 10 package.c:7448: Test failed: Expected "C:\\short\", got "C:\short\" package.c:7449: Test failed: Expected 10, got 9 package.c:7458: Test failed: Expected "C:\\short\", got "C:\short\" package.c:7459: Test failed: Expected 10, got 9 package.c:7468: Test failed: Expected "C:\\short\", got "C:\short\" package.c:7469: Test failed: Expected 10, got 9 package.c:7480: Test failed: Expected "C:\\one\", got "C:\one\" package.c:7481: Test failed: Expected 8, got 7 package.c:7492: Test failed: Expected "C:\\three\", got "C:\three\" package.c:7493: Test failed: Expected 10, got 9 package.c:7504: Test failed: Expected "C:\\five\", got "C:\five\" package.c:7505: Test failed: Expected 9, got 8 package.c:7516: Test failed: Expected "C:\\seven\", got "C:\seven\" package.c:7517: Test failed: Expected 10, got 9 package.c:7528: Test failed: Expected "C:\\nine\", got "C:\nine\" package.c:7529: Test failed: Expected 9, got 8 package.c:7540: Test failed: Expected "C:\\eleven\", got "C:\eleven\" package.c:7541: Test failed: Expected 11, got 10 package.c:7677: Test failed: Expected "C:\\", got "C:\" package.c:7678: Test failed: Expected 4, got 3 package.c:7689: Test failed: Expected "C:\\", got "C:\" package.c:7690: Test failed: Expected 4, got 3 package.c:7697: Test failed: Expected "C:\\", got "C:\" package.c:7698: Test failed: Expected 4, got 3 package.c:7795: Test failed: Expected "C:\\", got "C:\" package.c:7796: Test failed: Expected 4, got 3 package.c:7803: Test failed: Expected "C:\\", got "C:\" package.c:7804: Test failed: Expected 4, got 3 package.c:7811: Test failed: Expected "C:\\", got "C:\" package.c:7812: Test failed: Expected 4, got 3 package.c:7831: Test failed: Expected "C:\\", got "C:\" package.c:7832: Test failed: Expected 4, got 3 package.c:7839: Test failed: Expected "C:\\", got "C:\" package.c:7840: Test failed: Expected 4, got 3 package.c:7859: Test failed: Expected "C:\\", got "C:\" package.c:7860: Test failed: Expected 4, got 3 package.c:7867: Test failed: Expected "C:\\", got "C:\" package.c:7868: Test failed: Expected 4, got 3 package.c:7887: Test failed: Expected "C:\\", got "C:\" package.c:7888: Test failed: Expected 4, got 3 package.c:7895: Test failed: Expected "C:\\", got "C:\" package.c:7896: Test failed: Expected 4, got 3 === wvistau64 (32 bit package) === package.c:3985: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:3991: Test failed: Expected "E:\\FileName2", got "E:\FileName2" package.c:3997: Test failed: Expected "E:\\FileName3", got "E:\FileName3" package.c:4009: Test failed: Expected "E:\\FileName5", got "E:\FileName5" package.c:4015: Test failed: Expected "E:\\", got "E:\" package.c:4021: Test failed: Expected "E:\\", got "E:\" package.c:4037: Test failed: Expected "E:\\FileName8.dll", got "E:\FileName8.dll" package.c:4048: Test failed: Expected "E:\\FileName10.dll", got "E:\FileName10.dll" package.c:4507: Test failed: Expected ERROR_SUCCESS, got 1627 package.c:4599: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4610: Test failed: Expected "E:\\", got "E:\" package.c:4621: Test failed: Expected "E:\\", got "E:\" package.c:4671: Test failed: Expected "E:\\FileName3.dll", got "E:\FileName3.dll" package.c:4682: Test failed: Expected "E:\\FileName5.dll", got "E:\FileName5.dll" package.c:4697: Test failed: Expected "E:\\", got "E:\" package.c:4702: Test failed: Expected "", got "E:\" package.c:4718: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4727: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4977: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4988: Test failed: Expected "E:\\", got "E:\" package.c:4994: Test failed: Expected "E:\\", got "E:\" package.c:5015: Test failed: Expected "E:\\FileName2.dll", got "E:\FileName2.dll" package.c:5026: Test failed: Expected "E:\\FileName4.dll", got "E:\FileName4.dll" package.c:5266: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:5272: Test failed: Expected "E:\\", got "E:\" package.c:5289: Test failed: Expected "E:\\one\two\three\FileName2", got "E:\one\two\three\FileName2" package.c:5300: Test failed: Expected "E:\\one\two\three\FileName2", got "E:\one\two\three\FileName2" package.c:5308: Test failed: Expected "E:\\FileName3.dll", got "E:\FileName3.dll" package.c:5652: Test failed: Expected E:\\winetest-package.msi, got E:\winetest-package.msi package.c:6284: Test failed: Expected E:\\abelisaurus or empty string, got E:\abelisaurus package.c:6308: Test failed: Expected E:\\ or empty string, got E:\ package.c:6352: Test failed: Expected E:\\ or empty string, got E:\ package.c:6361: Test failed: Expected E:\\neosodon\ or empty string, got E:\neosodon\ package.c:6591: Test failed: Expected "E:\\", got "E:\" package.c:6592: Test failed: Expected 4, got 3 package.c:6599: Test failed: Expected "E:\\", got "E:\" package.c:6600: Test failed: Expected 4, got 3 package.c:6616: Test failed: Expected "E:\\", got "E:\" package.c:6617: Test failed: Expected 4, got 3 package.c:6623: Test failed: Expected "E:\\", got "E:\" package.c:6624: Test failed: Expected 4, got 3 package.c:6631: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6632: Test failed: Expected 14, got 13 package.c:6639: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6640: Test failed: Expected 19, got 18 package.c:6650: Test failed: Expected "E:\\", got "E:\" package.c:6651: Test failed: Expected 4, got 3 package.c:6658: Test failed: Expected "E:\\", got "E:\" package.c:6659: Test failed: Expected 4, got 3 package.c:6675: Test failed: Expected "E:\\", got "E:\" package.c:6676: Test failed: Expected 4, got 3 package.c:6682: Test failed: Expected "E:\\", got "E:\" package.c:6683: Test failed: Expected 4, got 3 package.c:6690: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6691: Test failed: Expected 14, got 13 package.c:6698: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6699: Test failed: Expected 19, got 18 package.c:6709: Test failed: Expected "E:\\", got "E:\" package.c:6710: Test failed: Expected 4, got 3 package.c:6717: Test failed: Expected "E:\\", got "E:\" package.c:6718: Test failed: Expected 4, got 3 package.c:6734: Test failed: Expected "E:\\", got "E:\" package.c:6735: Test failed: Expected 4, got 3 package.c:6741: Test failed: Expected "E:\\", got "E:\" package.c:6742: Test failed: Expected 4, got 3 package.c:6749: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6750: Test failed: Expected 14, got 13 package.c:6757: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6758: Test failed: Expected 19, got 18 package.c:6768: Test failed: Expected "E:\\", got "E:\" package.c:6769: Test failed: Expected 4, got 3 package.c:6776: Test failed: Expected "E:\\", got "E:\" package.c:6777: Test failed: Expected 4, got 3 package.c:6793: Test failed: Expected "E:\\", got "E:\" package.c:6794: Test failed: Expected 4, got 3 package.c:6800: Test failed: Expected "E:\\", got "E:\" package.c:6801: Test failed: Expected 4, got 3 package.c:6808: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6809: Test failed: Expected 14, got 13 package.c:6816: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6817: Test failed: Expected 19, got 18 package.c:6832: Test failed: Expected 4, got 3 package.c:6849: Test failed: Expected 4, got 3 package.c:6855: Test failed: Expected ERROR_MORE_DATA, got 0 package.c:6858: Test failed: Expected 4, got 3 package.c:6865: Test failed: Expected "E:\\", got "E:\" package.c:6866: Test failed: Expected 4, got 3 package.c:6877: Test failed: Expected "E:\\", got "E:\" package.c:6878: Test failed: Expected 4, got 3 package.c:6973: Test failed: Expected "E:\\", got "E:\" package.c:6974: Test failed: Expected 4, got 3 package.c:6981: Test failed: Expected "E:\\", got "E:\" package.c:6982: Test failed: Expected 4, got 3 package.c:6991: Test failed: Expected "E:\\", got "E:\" package.c:6992: Test failed: Expected 4, got 3 package.c:7000: Test failed: Expected "E:\\", got "E:\" package.c:7001: Test failed: Expected 4, got 3 package.c:7007: Test failed: Expected "E:\\", got "E:\" package.c:7008: Test failed: Expected 4, got 3 package.c:7015: Test failed: Expected "E:\\", got "E:\" package.c:7016: Test failed: Expected 4, got 3 package.c:7023: Test failed: Expected "E:\\", got "E:\" package.c:7024: Test failed: Expected 4, got 3 package.c:7034: Test failed: Expected "E:\\", got "E:\" package.c:7035: Test failed: Expected 4, got 3 package.c:7042: Test failed: Expected "E:\\", got "E:\" package.c:7043: Test failed: Expected 4, got 3 package.c:7052: Test failed: Expected "E:\\", got "E:\" package.c:7053: Test failed: Expected 4, got 3 package.c:7061: Test failed: Expected "E:\\", got "E:\" package.c:7062: Test failed: Expected 4, got 3 package.c:7068: Test failed: Expected "E:\\", got "E:\" package.c:7069: Test failed: Expected 4, got 3 package.c:7076: Test failed: Expected "E:\\", got "E:\" package.c:7077: Test failed: Expected 4, got 3 package.c:7084: Test failed: Expected "E:\\", got "E:\" package.c:7085: Test failed: Expected 4, got 3 package.c:7095: Test failed: Expected "E:\\", got "E:\" package.c:7096: Test failed: Expected 4, got 3 package.c:7103: Test failed: Expected "E:\\", got "E:\" package.c:7104: Test failed: Expected 4, got 3 package.c:7113: Test failed: Expected "E:\\", got "E:\" package.c:7114: Test failed: Expected 4, got 3 package.c:7122: Test failed: Expected "E:\\", got "E:\" package.c:7123: Test failed: Expected 4, got 3 package.c:7129: Test failed: Expected "E:\\", got "E:\" package.c:7130: Test failed: Expected 4, got 3 package.c:7137: Test failed: Expected "E:\\", got "E:\" package.c:7138: Test failed: Expected 4, got 3 package.c:7145: Test failed: Expected "E:\\", got "E:\" package.c:7146: Test failed: Expected 4, got 3 package.c:7156: Test failed: Expected "E:\\", got "E:\" package.c:7157: Test failed: Expected 4, got 3 package.c:7164: Test failed: Expected "E:\\", got "E:\" package.c:7165: Test failed: Expected 4, got 3 package.c:7174: Test failed: Expected "E:\\", got "E:\" package.c:7175: Test failed: Expected 4, got 3 package.c:7183: Test failed: Expected "E:\\", got "E:\" package.c:7184: Test failed: Expected 4, got 3 package.c:7190: Test failed: Expected "E:\\", got "E:\" package.c:7191: Test failed: Expected 4, got 3 package.c:7198: Test failed: Expected "E:\\", got "E:\" package.c:7199: Test failed: Expected 4, got 3 package.c:7206: Test failed: Expected "E:\\", got "E:\" package.c:7207: Test failed: Expected 4, got 3 package.c:7304: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7305: Test failed: Expected 9, got 8 package.c:7314: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7315: Test failed: Expected 9, got 8 package.c:7324: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7325: Test failed: Expected 9, got 8 package.c:7336: Test failed: Expected "E:\\two\", got "E:\two\" package.c:7337: Test failed: Expected 8, got 7 package.c:7348: Test failed: Expected "E:\\four\", got "E:\four\" package.c:7349: Test failed: Expected 9, got 8 package.c:7360: Test failed: Expected "E:\\six\", got "E:\six\" package.c:7361: Test failed: Expected 8, got 7 package.c:7372: Test failed: Expected "E:\\eight\", got "E:\eight\" package.c:7373: Test failed: Expected 10, got 9 package.c:7384: Test failed: Expected "E:\\ten\", got "E:\ten\" package.c:7385: Test failed: Expected 8, got 7 package.c:7396: Test failed: Expected "E:\\twelve\", got "E:\twelve\" package.c:7397: Test failed: Expected 11, got 10 package.c:7448: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7449: Test failed: Expected 10, got 9 package.c:7458: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7459: Test failed: Expected 10, got 9 package.c:7468: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7469: Test failed: Expected 10, got 9 package.c:7480: Test failed: Expected "E:\\one\", got "E:\one\" package.c:7481: Test failed: Expected 8, got 7 package.c:7492: Test failed: Expected "E:\\three\", got "E:\three\" package.c:7493: Test failed: Expected 10, got 9 package.c:7504: Test failed: Expected "E:\\five\", got "E:\five\" package.c:7505: Test failed: Expected 9, got 8 package.c:7516: Test failed: Expected "E:\\seven\", got "E:\seven\" package.c:7517: Test failed: Expected 10, got 9 package.c:7528: Test failed: Expected "E:\\nine\", got "E:\nine\" package.c:7529: Test failed: Expected 9, got 8 package.c:7540: Test failed: Expected "E:\\eleven\", got "E:\eleven\" package.c:7541: Test failed: Expected 11, got 10 package.c:7677: Test failed: Expected "E:\\", got "E:\" package.c:7678: Test failed: Expected 4, got 3 package.c:7689: Test failed: Expected "E:\\", got "E:\" package.c:7690: Test failed: Expected 4, got 3 package.c:7697: Test failed: Expected "E:\\", got "E:\" package.c:7698: Test failed: Expected 4, got 3 package.c:7795: Test failed: Expected "E:\\", got "E:\" package.c:7796: Test failed: Expected 4, got 3 package.c:7803: Test failed: Expected "E:\\", got "E:\" package.c:7804: Test failed: Expected 4, got 3 package.c:7811: Test failed: Expected "E:\\", got "E:\" package.c:7812: Test failed: Expected 4, got 3 package.c:7831: Test failed: Expected "E:\\", got "E:\" package.c:7832: Test failed: Expected 4, got 3 package.c:7839: Test failed: Expected "E:\\", got "E:\" package.c:7840: Test failed: Expected 4, got 3 package.c:7859: Test failed: Expected "E:\\", got "E:\" package.c:7860: Test failed: Expected 4, got 3 package.c:7867: Test failed: Expected "E:\\", got "E:\" package.c:7868: Test failed: Expected 4, got 3 package.c:7887: Test failed: Expected "E:\\", got "E:\" package.c:7888: Test failed: Expected 4, got 3 package.c:7895: Test failed: Expected "E:\\", got "E:\" package.c:7896: Test failed: Expected 4, got 3 === w7u (32 bit package) === The test timed out === wvistau64 (64 bit package) === package.c:3985: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:3991: Test failed: Expected "E:\\FileName2", got "E:\FileName2" package.c:3997: Test failed: Expected "E:\\FileName3", got "E:\FileName3" package.c:4009: Test failed: Expected "E:\\FileName5", got "E:\FileName5" package.c:4015: Test failed: Expected "E:\\", got "E:\" package.c:4021: Test failed: Expected "E:\\", got "E:\" package.c:4037: Test failed: Expected "E:\\FileName8.dll", got "E:\FileName8.dll" package.c:4048: Test failed: Expected "E:\\FileName10.dll", got "E:\FileName10.dll" package.c:4507: Test failed: Expected ERROR_SUCCESS, got 1627 package.c:4599: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4610: Test failed: Expected "E:\\", got "E:\" package.c:4621: Test failed: Expected "E:\\", got "E:\" package.c:4671: Test failed: Expected "E:\\FileName3.dll", got "E:\FileName3.dll" package.c:4682: Test failed: Expected "E:\\FileName5.dll", got "E:\FileName5.dll" package.c:4697: Test failed: Expected "E:\\", got "E:\" package.c:4702: Test failed: Expected "", got "E:\" package.c:4718: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4727: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4977: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4988: Test failed: Expected "E:\\", got "E:\" package.c:4994: Test failed: Expected "E:\\", got "E:\" package.c:5015: Test failed: Expected "E:\\FileName2.dll", got "E:\FileName2.dll" package.c:5026: Test failed: Expected "E:\\FileName4.dll", got "E:\FileName4.dll" package.c:5266: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:5272: Test failed: Expected "E:\\", got "E:\" package.c:5289: Test failed: Expected "E:\\one\two\three\FileName2", got "E:\one\two\three\FileName2" package.c:5300: Test failed: Expected "E:\\one\two\three\FileName2", got "E:\one\two\three\FileName2" package.c:5308: Test failed: Expected "E:\\FileName3.dll", got "E:\FileName3.dll" package.c:5652: Test failed: Expected E:\\winetest-package.msi, got E:\winetest-package.msi package.c:6284: Test failed: Expected E:\\abelisaurus or empty string, got E:\abelisaurus package.c:6308: Test failed: Expected E:\\ or empty string, got E:\ package.c:6352: Test failed: Expected E:\\ or empty string, got E:\ package.c:6361: Test failed: Expected E:\\neosodon\ or empty string, got E:\neosodon\ package.c:6591: Test failed: Expected "E:\\", got "E:\" package.c:6592: Test failed: Expected 4, got 3 package.c:6599: Test failed: Expected "E:\\", got "E:\" package.c:6600: Test failed: Expected 4, got 3 package.c:6616: Test failed: Expected "E:\\", got "E:\" package.c:6617: Test failed: Expected 4, got 3 package.c:6623: Test failed: Expected "E:\\", got "E:\" package.c:6624: Test failed: Expected 4, got 3 package.c:6631: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6632: Test failed: Expected 14, got 13 package.c:6639: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6640: Test failed: Expected 19, got 18 package.c:6650: Test failed: Expected "E:\\", got "E:\" package.c:6651: Test failed: Expected 4, got 3 package.c:6658: Test failed: Expected "E:\\", got "E:\" package.c:6659: Test failed: Expected 4, got 3 package.c:6675: Test failed: Expected "E:\\", got "E:\" package.c:6676: Test failed: Expected 4, got 3 package.c:6682: Test failed: Expected "E:\\", got "E:\" package.c:6683: Test failed: Expected 4, got 3 package.c:6690: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6691: Test failed: Expected 14, got 13 package.c:6698: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6699: Test failed: Expected 19, got 18 package.c:6709: Test failed: Expected "E:\\", got "E:\" package.c:6710: Test failed: Expected 4, got 3 package.c:6717: Test failed: Expected "E:\\", got "E:\" package.c:6718: Test failed: Expected 4, got 3 package.c:6734: Test failed: Expected "E:\\", got "E:\" package.c:6735: Test failed: Expected 4, got 3 package.c:6741: Test failed: Expected "E:\\", got "E:\" package.c:6742: Test failed: Expected 4, got 3 package.c:6749: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6750: Test failed: Expected 14, got 13 package.c:6757: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6758: Test failed: Expected 19, got 18 package.c:6768: Test failed: Expected "E:\\", got "E:\" package.c:6769: Test failed: Expected 4, got 3 package.c:6776: Test failed: Expected "E:\\", got "E:\" package.c:6777: Test failed: Expected 4, got 3 package.c:6793: Test failed: Expected "E:\\", got "E:\" package.c:6794: Test failed: Expected 4, got 3 package.c:6800: Test failed: Expected "E:\\", got "E:\" package.c:6801: Test failed: Expected 4, got 3 package.c:6808: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6809: Test failed: Expected 14, got 13 package.c:6816: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6817: Test failed: Expected 19, got 18 package.c:6832: Test failed: Expected 4, got 3 package.c:6849: Test failed: Expected 4, got 3 package.c:6855: Test failed: Expected ERROR_MORE_DATA, got 0 package.c:6858: Test failed: Expected 4, got 3 package.c:6865: Test failed: Expected "E:\\", got "E:\" package.c:6866: Test failed: Expected 4, got 3 package.c:6877: Test failed: Expected "E:\\", got "E:\" package.c:6878: Test failed: Expected 4, got 3 package.c:6973: Test failed: Expected "E:\\", got "E:\" package.c:6974: Test failed: Expected 4, got 3 package.c:6981: Test failed: Expected "E:\\", got "E:\" package.c:6982: Test failed: Expected 4, got 3 package.c:6991: Test failed: Expected "E:\\", got "E:\" package.c:6992: Test failed: Expected 4, got 3 package.c:7000: Test failed: Expected "E:\\", got "E:\" package.c:7001: Test failed: Expected 4, got 3 package.c:7007: Test failed: Expected "E:\\", got "E:\" package.c:7008: Test failed: Expected 4, got 3 package.c:7015: Test failed: Expected "E:\\", got "E:\" package.c:7016: Test failed: Expected 4, got 3 package.c:7023: Test failed: Expected "E:\\", got "E:\" package.c:7024: Test failed: Expected 4, got 3 package.c:7034: Test failed: Expected "E:\\", got "E:\" package.c:7035: Test failed: Expected 4, got 3 package.c:7042: Test failed: Expected "E:\\", got "E:\" package.c:7043: Test failed: Expected 4, got 3 package.c:7052: Test failed: Expected "E:\\", got "E:\" package.c:7053: Test failed: Expected 4, got 3 package.c:7061: Test failed: Expected "E:\\", got "E:\" package.c:7062: Test failed: Expected 4, got 3 package.c:7068: Test failed: Expected "E:\\", got "E:\" package.c:7069: Test failed: Expected 4, got 3 package.c:7076: Test failed: Expected "E:\\", got "E:\" package.c:7077: Test failed: Expected 4, got 3 package.c:7084: Test failed: Expected "E:\\", got "E:\" package.c:7085: Test failed: Expected 4, got 3 package.c:7095: Test failed: Expected "E:\\", got "E:\" package.c:7096: Test failed: Expected 4, got 3 package.c:7103: Test failed: Expected "E:\\", got "E:\" package.c:7104: Test failed: Expected 4, got 3 package.c:7113: Test failed: Expected "E:\\", got "E:\" package.c:7114: Test failed: Expected 4, got 3 package.c:7122: Test failed: Expected "E:\\", got "E:\" package.c:7123: Test failed: Expected 4, got 3 package.c:7129: Test failed: Expected "E:\\", got "E:\" package.c:7130: Test failed: Expected 4, got 3 package.c:7137: Test failed: Expected "E:\\", got "E:\" package.c:7138: Test failed: Expected 4, got 3 package.c:7145: Test failed: Expected "E:\\", got "E:\" package.c:7146: Test failed: Expected 4, got 3 package.c:7156: Test failed: Expected "E:\\", got "E:\" package.c:7157: Test failed: Expected 4, got 3 package.c:7164: Test failed: Expected "E:\\", got "E:\" package.c:7165: Test failed: Expected 4, got 3 package.c:7174: Test failed: Expected "E:\\", got "E:\" package.c:7175: Test failed: Expected 4, got 3 package.c:7183: Test failed: Expected "E:\\", got "E:\" package.c:7184: Test failed: Expected 4, got 3 package.c:7190: Test failed: Expected "E:\\", got "E:\" package.c:7191: Test failed: Expected 4, got 3 package.c:7198: Test failed: Expected "E:\\", got "E:\" package.c:7199: Test failed: Expected 4, got 3 package.c:7206: Test failed: Expected "E:\\", got "E:\" package.c:7207: Test failed: Expected 4, got 3 package.c:7304: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7305: Test failed: Expected 9, got 8 package.c:7314: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7315: Test failed: Expected 9, got 8 package.c:7324: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7325: Test failed: Expected 9, got 8 package.c:7336: Test failed: Expected "E:\\two\", got "E:\two\" package.c:7337: Test failed: Expected 8, got 7 package.c:7348: Test failed: Expected "E:\\four\", got "E:\four\" package.c:7349: Test failed: Expected 9, got 8 package.c:7360: Test failed: Expected "E:\\six\", got "E:\six\" package.c:7361: Test failed: Expected 8, got 7 package.c:7372: Test failed: Expected "E:\\eight\", got "E:\eight\" package.c:7373: Test failed: Expected 10, got 9 package.c:7384: Test failed: Expected "E:\\ten\", got "E:\ten\" package.c:7385: Test failed: Expected 8, got 7 package.c:7396: Test failed: Expected "E:\\twelve\", got "E:\twelve\" package.c:7397: Test failed: Expected 11, got 10 package.c:7448: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7449: Test failed: Expected 10, got 9 package.c:7458: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7459: Test failed: Expected 10, got 9 package.c:7468: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7469: Test failed: Expected 10, got 9 package.c:7480: Test failed: Expected "E:\\one\", got "E:\one\" package.c:7481: Test failed: Expected 8, got 7 package.c:7492: Test failed: Expected "E:\\three\", got "E:\three\" package.c:7493: Test failed: Expected 10, got 9 package.c:7504: Test failed: Expected "E:\\five\", got "E:\five\" package.c:7505: Test failed: Expected 9, got 8 package.c:7516: Test failed: Expected "E:\\seven\", got "E:\seven\" package.c:7517: Test failed: Expected 10, got 9 package.c:7528: Test failed: Expected "E:\\nine\", got "E:\nine\" package.c:7529: Test failed: Expected 9, got 8 package.c:7540: Test failed: Expected "E:\\eleven\", got "E:\eleven\" package.c:7541: Test failed: Expected 11, got 10 package.c:7677: Test failed: Expected "E:\\", got "E:\" package.c:7678: Test failed: Expected 4, got 3 package.c:7689: Test failed: Expected "E:\\", got "E:\" package.c:7690: Test failed: Expected 4, got 3 package.c:7697: Test failed: Expected "E:\\", got "E:\" package.c:7698: Test failed: Expected 4, got 3 package.c:7795: Test failed: Expected "E:\\", got "E:\" package.c:7796: Test failed: Expected 4, got 3 package.c:7803: Test failed: Expected "E:\\", got "E:\" package.c:7804: Test failed: Expected 4, got 3 package.c:7811: Test failed: Expected "E:\\", got "E:\" package.c:7812: Test failed: Expected 4, got 3 package.c:7831: Test failed: Expected "E:\\", got "E:\" package.c:7832: Test failed: Expected 4, got 3 package.c:7839: Test failed: Expected "E:\\", got "E:\" package.c:7840: Test failed: Expected 4, got 3 package.c:7859: Test failed: Expected "E:\\", got "E:\" package.c:7860: Test failed: Expected 4, got 3 package.c:7867: Test failed: Expected "E:\\", got "E:\" package.c:7868: Test failed: Expected 4, got 3 package.c:7887: Test failed: Expected "E:\\", got "E:\" package.c:7888: Test failed: Expected 4, got 3 package.c:7895: Test failed: Expected "E:\\", got "E:\" package.c:7896: Test failed: Expected 4, got 3

2 1

Re: [PATCH 4/4] msi: Add more feature state tests
by Marvin 24 Jul '14

24 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8088 Your paranoid android. === w2000pro (32 bit package) === package.c:4034: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:4040: Test failed: Expected "C:\\FileName2", got "C:\FileName2" package.c:4046: Test failed: Expected "C:\\FileName3", got "C:\FileName3" package.c:4058: Test failed: Expected "C:\\FileName5", got "C:\FileName5" package.c:4064: Test failed: Expected "C:\\", got "C:\" package.c:4070: Test failed: Expected "C:\\", got "C:\" package.c:4086: Test failed: Expected "C:\\FileName8.dll", got "C:\FileName8.dll" package.c:4097: Test failed: Expected "C:\\FileName10.dll", got "C:\FileName10.dll" package.c:4556: Test failed: Expected ERROR_SUCCESS, got 1627 package.c:4648: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:4659: Test failed: Expected "C:\\", got "C:\" package.c:4670: Test failed: Expected "C:\\", got "C:\" package.c:4720: Test failed: Expected "C:\\FileName3.dll", got "C:\FileName3.dll" package.c:4731: Test failed: Expected "C:\\FileName5.dll", got "C:\FileName5.dll" package.c:4746: Test failed: Expected "C:\\", got "C:\" package.c:4751: Test failed: Expected "", got "C:\" package.c:4767: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:4776: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:5026: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:5037: Test failed: Expected "C:\\", got "C:\" package.c:5043: Test failed: Expected "C:\\", got "C:\" package.c:5064: Test failed: Expected "C:\\FileName2.dll", got "C:\FileName2.dll" package.c:5075: Test failed: Expected "C:\\FileName4.dll", got "C:\FileName4.dll" package.c:5315: Test failed: Expected "C:\\FileName1", got "C:\FileName1" package.c:5321: Test failed: Expected "C:\\", got "C:\" package.c:5338: Test failed: Expected "C:\\one\two\three\FileName2", got "C:\one\two\three\FileName2" package.c:5349: Test failed: Expected "C:\\one\two\three\FileName2", got "C:\one\two\three\FileName2" package.c:5357: Test failed: Expected "C:\\FileName3.dll", got "C:\FileName3.dll" package.c:5701: Test failed: Expected C:\\winetest-package.msi, got C:\winetest-package.msi package.c:6333: Test failed: Expected C:\\abelisaurus or empty string, got C:\abelisaurus package.c:6357: Test failed: Expected C:\\ or empty string, got C:\ package.c:6401: Test failed: Expected C:\\ or empty string, got C:\ package.c:6410: Test failed: Expected C:\\neosodon\ or empty string, got C:\neosodon\ package.c:6640: Test failed: Expected "C:\\", got "C:\" package.c:6641: Test failed: Expected 4, got 3 package.c:6648: Test failed: Expected "C:\\", got "C:\" package.c:6649: Test failed: Expected 4, got 3 package.c:6665: Test failed: Expected "C:\\", got "C:\" package.c:6666: Test failed: Expected 4, got 3 package.c:6672: Test failed: Expected "C:\\", got "C:\" package.c:6673: Test failed: Expected 4, got 3 package.c:6680: Test failed: Expected "C:\\subsource\", got "C:\subsource\" package.c:6681: Test failed: Expected 14, got 13 package.c:6688: Test failed: Expected "C:\\subsource\sub2\", got "C:\subsource\sub2\" package.c:6689: Test failed: Expected 19, got 18 package.c:6699: Test failed: Expected "C:\\", got "C:\" package.c:6700: Test failed: Expected 4, got 3 package.c:6707: Test failed: Expected "C:\\", got "C:\" package.c:6708: Test failed: Expected 4, got 3 package.c:6724: Test failed: Expected "C:\\", got "C:\" package.c:6725: Test failed: Expected 4, got 3 package.c:6731: Test failed: Expected "C:\\", got "C:\" package.c:6732: Test failed: Expected 4, got 3 package.c:6739: Test failed: Expected "C:\\subsource\", got "C:\subsource\" package.c:6740: Test failed: Expected 14, got 13 package.c:6747: Test failed: Expected "C:\\subsource\sub2\", got "C:\subsource\sub2\" package.c:6748: Test failed: Expected 19, got 18 package.c:6758: Test failed: Expected "C:\\", got "C:\" package.c:6759: Test failed: Expected 4, got 3 package.c:6766: Test failed: Expected "C:\\", got "C:\" package.c:6767: Test failed: Expected 4, got 3 package.c:6783: Test failed: Expected "C:\\", got "C:\" package.c:6784: Test failed: Expected 4, got 3 package.c:6790: Test failed: Expected "C:\\", got "C:\" package.c:6791: Test failed: Expected 4, got 3 package.c:6798: Test failed: Expected "C:\\subsource\", got "C:\subsource\" package.c:6799: Test failed: Expected 14, got 13 package.c:6806: Test failed: Expected "C:\\subsource\sub2\", got "C:\subsource\sub2\" package.c:6807: Test failed: Expected 19, got 18 package.c:6817: Test failed: Expected "C:\\", got "C:\" package.c:6818: Test failed: Expected 4, got 3 package.c:6825: Test failed: Expected "C:\\", got "C:\" package.c:6826: Test failed: Expected 4, got 3 package.c:6842: Test failed: Expected "C:\\", got "C:\" package.c:6843: Test failed: Expected 4, got 3 package.c:6849: Test failed: Expected "C:\\", got "C:\" package.c:6850: Test failed: Expected 4, got 3 package.c:6857: Test failed: Expected "C:\\subsource\", got "C:\subsource\" package.c:6858: Test failed: Expected 14, got 13 package.c:6865: Test failed: Expected "C:\\subsource\sub2\", got "C:\subsource\sub2\" package.c:6866: Test failed: Expected 19, got 18 package.c:6881: Test failed: Expected 4, got 3 package.c:6898: Test failed: Expected 4, got 3 package.c:6904: Test failed: Expected ERROR_MORE_DATA, got 0 package.c:6907: Test failed: Expected 4, got 3 package.c:6914: Test failed: Expected "C:\\", got "C:\" package.c:6915: Test failed: Expected 4, got 3 package.c:6926: Test failed: Expected "C:\\", got "C:\" package.c:6927: Test failed: Expected 4, got 3 package.c:7022: Test failed: Expected "C:\\", got "C:\" package.c:7023: Test failed: Expected 4, got 3 package.c:7030: Test failed: Expected "C:\\", got "C:\" package.c:7031: Test failed: Expected 4, got 3 package.c:7040: Test failed: Expected "C:\\", got "C:\" package.c:7041: Test failed: Expected 4, got 3 package.c:7049: Test failed: Expected "C:\\", got "C:\" package.c:7050: Test failed: Expected 4, got 3 package.c:7056: Test failed: Expected "C:\\", got "C:\" package.c:7057: Test failed: Expected 4, got 3 package.c:7064: Test failed: Expected "C:\\", got "C:\" package.c:7065: Test failed: Expected 4, got 3 package.c:7072: Test failed: Expected "C:\\", got "C:\" package.c:7073: Test failed: Expected 4, got 3 package.c:7083: Test failed: Expected "C:\\", got "C:\" package.c:7084: Test failed: Expected 4, got 3 package.c:7091: Test failed: Expected "C:\\", got "C:\" package.c:7092: Test failed: Expected 4, got 3 package.c:7101: Test failed: Expected "C:\\", got "C:\" package.c:7102: Test failed: Expected 4, got 3 package.c:7110: Test failed: Expected "C:\\", got "C:\" package.c:7111: Test failed: Expected 4, got 3 package.c:7117: Test failed: Expected "C:\\", got "C:\" package.c:7118: Test failed: Expected 4, got 3 package.c:7125: Test failed: Expected "C:\\", got "C:\" package.c:7126: Test failed: Expected 4, got 3 package.c:7133: Test failed: Expected "C:\\", got "C:\" package.c:7134: Test failed: Expected 4, got 3 package.c:7144: Test failed: Expected "C:\\", got "C:\" package.c:7145: Test failed: Expected 4, got 3 package.c:7152: Test failed: Expected "C:\\", got "C:\" package.c:7153: Test failed: Expected 4, got 3 package.c:7162: Test failed: Expected "C:\\", got "C:\" package.c:7163: Test failed: Expected 4, got 3 package.c:7171: Test failed: Expected "C:\\", got "C:\" package.c:7172: Test failed: Expected 4, got 3 package.c:7178: Test failed: Expected "C:\\", got "C:\" package.c:7179: Test failed: Expected 4, got 3 package.c:7186: Test failed: Expected "C:\\", got "C:\" package.c:7187: Test failed: Expected 4, got 3 package.c:7194: Test failed: Expected "C:\\", got "C:\" package.c:7195: Test failed: Expected 4, got 3 package.c:7205: Test failed: Expected "C:\\", got "C:\" package.c:7206: Test failed: Expected 4, got 3 package.c:7213: Test failed: Expected "C:\\", got "C:\" package.c:7214: Test failed: Expected 4, got 3 package.c:7223: Test failed: Expected "C:\\", got "C:\" package.c:7224: Test failed: Expected 4, got 3 package.c:7232: Test failed: Expected "C:\\", got "C:\" package.c:7233: Test failed: Expected 4, got 3 package.c:7239: Test failed: Expected "C:\\", got "C:\" package.c:7240: Test failed: Expected 4, got 3 package.c:7247: Test failed: Expected "C:\\", got "C:\" package.c:7248: Test failed: Expected 4, got 3 package.c:7255: Test failed: Expected "C:\\", got "C:\" package.c:7256: Test failed: Expected 4, got 3 package.c:7353: Test failed: Expected "C:\\long\", got "C:\long\" package.c:7354: Test failed: Expected 9, got 8 package.c:7363: Test failed: Expected "C:\\long\", got "C:\long\" package.c:7364: Test failed: Expected 9, got 8 package.c:7373: Test failed: Expected "C:\\long\", got "C:\long\" package.c:7374: Test failed: Expected 9, got 8 package.c:7385: Test failed: Expected "C:\\two\", got "C:\two\" package.c:7386: Test failed: Expected 8, got 7 package.c:7397: Test failed: Expected "C:\\four\", got "C:\four\" package.c:7398: Test failed: Expected 9, got 8 package.c:7409: Test failed: Expected "C:\\six\", got "C:\six\" package.c:7410: Test failed: Expected 8, got 7 package.c:7421: Test failed: Expected "C:\\eight\", got "C:\eight\" package.c:7422: Test failed: Expected 10, got 9 package.c:7433: Test failed: Expected "C:\\ten\", got "C:\ten\" package.c:7434: Test failed: Expected 8, got 7 package.c:7445: Test failed: Expected "C:\\twelve\", got "C:\twelve\" package.c:7446: Test failed: Expected 11, got 10 package.c:7497: Test failed: Expected "C:\\short\", got "C:\short\" package.c:7498: Test failed: Expected 10, got 9 package.c:7507: Test failed: Expected "C:\\short\", got "C:\short\" package.c:7508: Test failed: Expected 10, got 9 package.c:7517: Test failed: Expected "C:\\short\", got "C:\short\" package.c:7518: Test failed: Expected 10, got 9 package.c:7529: Test failed: Expected "C:\\one\", got "C:\one\" package.c:7530: Test failed: Expected 8, got 7 package.c:7541: Test failed: Expected "C:\\three\", got "C:\three\" package.c:7542: Test failed: Expected 10, got 9 package.c:7553: Test failed: Expected "C:\\five\", got "C:\five\" package.c:7554: Test failed: Expected 9, got 8 package.c:7565: Test failed: Expected "C:\\seven\", got "C:\seven\" package.c:7566: Test failed: Expected 10, got 9 package.c:7577: Test failed: Expected "C:\\nine\", got "C:\nine\" package.c:7578: Test failed: Expected 9, got 8 package.c:7589: Test failed: Expected "C:\\eleven\", got "C:\eleven\" package.c:7590: Test failed: Expected 11, got 10 package.c:7726: Test failed: Expected "C:\\", got "C:\" package.c:7727: Test failed: Expected 4, got 3 package.c:7738: Test failed: Expected "C:\\", got "C:\" package.c:7739: Test failed: Expected 4, got 3 package.c:7746: Test failed: Expected "C:\\", got "C:\" package.c:7747: Test failed: Expected 4, got 3 package.c:7844: Test failed: Expected "C:\\", got "C:\" package.c:7845: Test failed: Expected 4, got 3 package.c:7852: Test failed: Expected "C:\\", got "C:\" package.c:7853: Test failed: Expected 4, got 3 package.c:7860: Test failed: Expected "C:\\", got "C:\" package.c:7861: Test failed: Expected 4, got 3 package.c:7880: Test failed: Expected "C:\\", got "C:\" package.c:7881: Test failed: Expected 4, got 3 package.c:7888: Test failed: Expected "C:\\", got "C:\" package.c:7889: Test failed: Expected 4, got 3 package.c:7908: Test failed: Expected "C:\\", got "C:\" package.c:7909: Test failed: Expected 4, got 3 package.c:7916: Test failed: Expected "C:\\", got "C:\" package.c:7917: Test failed: Expected 4, got 3 package.c:7936: Test failed: Expected "C:\\", got "C:\" package.c:7937: Test failed: Expected 4, got 3 package.c:7944: Test failed: Expected "C:\\", got "C:\" package.c:7945: Test failed: Expected 4, got 3 === wvistau64 (32 bit package) === package.c:4034: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4040: Test failed: Expected "E:\\FileName2", got "E:\FileName2" package.c:4046: Test failed: Expected "E:\\FileName3", got "E:\FileName3" package.c:4058: Test failed: Expected "E:\\FileName5", got "E:\FileName5" package.c:4064: Test failed: Expected "E:\\", got "E:\" package.c:4070: Test failed: Expected "E:\\", got "E:\" package.c:4086: Test failed: Expected "E:\\FileName8.dll", got "E:\FileName8.dll" package.c:4097: Test failed: Expected "E:\\FileName10.dll", got "E:\FileName10.dll" package.c:4556: Test failed: Expected ERROR_SUCCESS, got 1627 package.c:4648: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4659: Test failed: Expected "E:\\", got "E:\" package.c:4670: Test failed: Expected "E:\\", got "E:\" package.c:4720: Test failed: Expected "E:\\FileName3.dll", got "E:\FileName3.dll" package.c:4731: Test failed: Expected "E:\\FileName5.dll", got "E:\FileName5.dll" package.c:4746: Test failed: Expected "E:\\", got "E:\" package.c:4751: Test failed: Expected "", got "E:\" package.c:4767: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4776: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:5026: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:5037: Test failed: Expected "E:\\", got "E:\" package.c:5043: Test failed: Expected "E:\\", got "E:\" package.c:5064: Test failed: Expected "E:\\FileName2.dll", got "E:\FileName2.dll" package.c:5075: Test failed: Expected "E:\\FileName4.dll", got "E:\FileName4.dll" package.c:5315: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:5321: Test failed: Expected "E:\\", got "E:\" package.c:5338: Test failed: Expected "E:\\one\two\three\FileName2", got "E:\one\two\three\FileName2" package.c:5349: Test failed: Expected "E:\\one\two\three\FileName2", got "E:\one\two\three\FileName2" package.c:5357: Test failed: Expected "E:\\FileName3.dll", got "E:\FileName3.dll" package.c:5701: Test failed: Expected E:\\winetest-package.msi, got E:\winetest-package.msi package.c:6333: Test failed: Expected E:\\abelisaurus or empty string, got E:\abelisaurus package.c:6357: Test failed: Expected E:\\ or empty string, got E:\ package.c:6401: Test failed: Expected E:\\ or empty string, got E:\ package.c:6410: Test failed: Expected E:\\neosodon\ or empty string, got E:\neosodon\ package.c:6640: Test failed: Expected "E:\\", got "E:\" package.c:6641: Test failed: Expected 4, got 3 package.c:6648: Test failed: Expected "E:\\", got "E:\" package.c:6649: Test failed: Expected 4, got 3 package.c:6665: Test failed: Expected "E:\\", got "E:\" package.c:6666: Test failed: Expected 4, got 3 package.c:6672: Test failed: Expected "E:\\", got "E:\" package.c:6673: Test failed: Expected 4, got 3 package.c:6680: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6681: Test failed: Expected 14, got 13 package.c:6688: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6689: Test failed: Expected 19, got 18 package.c:6699: Test failed: Expected "E:\\", got "E:\" package.c:6700: Test failed: Expected 4, got 3 package.c:6707: Test failed: Expected "E:\\", got "E:\" package.c:6708: Test failed: Expected 4, got 3 package.c:6724: Test failed: Expected "E:\\", got "E:\" package.c:6725: Test failed: Expected 4, got 3 package.c:6731: Test failed: Expected "E:\\", got "E:\" package.c:6732: Test failed: Expected 4, got 3 package.c:6739: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6740: Test failed: Expected 14, got 13 package.c:6747: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6748: Test failed: Expected 19, got 18 package.c:6758: Test failed: Expected "E:\\", got "E:\" package.c:6759: Test failed: Expected 4, got 3 package.c:6766: Test failed: Expected "E:\\", got "E:\" package.c:6767: Test failed: Expected 4, got 3 package.c:6783: Test failed: Expected "E:\\", got "E:\" package.c:6784: Test failed: Expected 4, got 3 package.c:6790: Test failed: Expected "E:\\", got "E:\" package.c:6791: Test failed: Expected 4, got 3 package.c:6798: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6799: Test failed: Expected 14, got 13 package.c:6806: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6807: Test failed: Expected 19, got 18 package.c:6817: Test failed: Expected "E:\\", got "E:\" package.c:6818: Test failed: Expected 4, got 3 package.c:6825: Test failed: Expected "E:\\", got "E:\" package.c:6826: Test failed: Expected 4, got 3 package.c:6842: Test failed: Expected "E:\\", got "E:\" package.c:6843: Test failed: Expected 4, got 3 package.c:6849: Test failed: Expected "E:\\", got "E:\" package.c:6850: Test failed: Expected 4, got 3 package.c:6857: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6858: Test failed: Expected 14, got 13 package.c:6865: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6866: Test failed: Expected 19, got 18 package.c:6881: Test failed: Expected 4, got 3 package.c:6898: Test failed: Expected 4, got 3 package.c:6904: Test failed: Expected ERROR_MORE_DATA, got 0 package.c:6907: Test failed: Expected 4, got 3 package.c:6914: Test failed: Expected "E:\\", got "E:\" package.c:6915: Test failed: Expected 4, got 3 package.c:6926: Test failed: Expected "E:\\", got "E:\" package.c:6927: Test failed: Expected 4, got 3 package.c:7022: Test failed: Expected "E:\\", got "E:\" package.c:7023: Test failed: Expected 4, got 3 package.c:7030: Test failed: Expected "E:\\", got "E:\" package.c:7031: Test failed: Expected 4, got 3 package.c:7040: Test failed: Expected "E:\\", got "E:\" package.c:7041: Test failed: Expected 4, got 3 package.c:7049: Test failed: Expected "E:\\", got "E:\" package.c:7050: Test failed: Expected 4, got 3 package.c:7056: Test failed: Expected "E:\\", got "E:\" package.c:7057: Test failed: Expected 4, got 3 package.c:7064: Test failed: Expected "E:\\", got "E:\" package.c:7065: Test failed: Expected 4, got 3 package.c:7072: Test failed: Expected "E:\\", got "E:\" package.c:7073: Test failed: Expected 4, got 3 package.c:7083: Test failed: Expected "E:\\", got "E:\" package.c:7084: Test failed: Expected 4, got 3 package.c:7091: Test failed: Expected "E:\\", got "E:\" package.c:7092: Test failed: Expected 4, got 3 package.c:7101: Test failed: Expected "E:\\", got "E:\" package.c:7102: Test failed: Expected 4, got 3 package.c:7110: Test failed: Expected "E:\\", got "E:\" package.c:7111: Test failed: Expected 4, got 3 package.c:7117: Test failed: Expected "E:\\", got "E:\" package.c:7118: Test failed: Expected 4, got 3 package.c:7125: Test failed: Expected "E:\\", got "E:\" package.c:7126: Test failed: Expected 4, got 3 package.c:7133: Test failed: Expected "E:\\", got "E:\" package.c:7134: Test failed: Expected 4, got 3 package.c:7144: Test failed: Expected "E:\\", got "E:\" package.c:7145: Test failed: Expected 4, got 3 package.c:7152: Test failed: Expected "E:\\", got "E:\" package.c:7153: Test failed: Expected 4, got 3 package.c:7162: Test failed: Expected "E:\\", got "E:\" package.c:7163: Test failed: Expected 4, got 3 package.c:7171: Test failed: Expected "E:\\", got "E:\" package.c:7172: Test failed: Expected 4, got 3 package.c:7178: Test failed: Expected "E:\\", got "E:\" package.c:7179: Test failed: Expected 4, got 3 package.c:7186: Test failed: Expected "E:\\", got "E:\" package.c:7187: Test failed: Expected 4, got 3 package.c:7194: Test failed: Expected "E:\\", got "E:\" package.c:7195: Test failed: Expected 4, got 3 package.c:7205: Test failed: Expected "E:\\", got "E:\" package.c:7206: Test failed: Expected 4, got 3 package.c:7213: Test failed: Expected "E:\\", got "E:\" package.c:7214: Test failed: Expected 4, got 3 package.c:7223: Test failed: Expected "E:\\", got "E:\" package.c:7224: Test failed: Expected 4, got 3 package.c:7232: Test failed: Expected "E:\\", got "E:\" package.c:7233: Test failed: Expected 4, got 3 package.c:7239: Test failed: Expected "E:\\", got "E:\" package.c:7240: Test failed: Expected 4, got 3 package.c:7247: Test failed: Expected "E:\\", got "E:\" package.c:7248: Test failed: Expected 4, got 3 package.c:7255: Test failed: Expected "E:\\", got "E:\" package.c:7256: Test failed: Expected 4, got 3 package.c:7353: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7354: Test failed: Expected 9, got 8 package.c:7363: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7364: Test failed: Expected 9, got 8 package.c:7373: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7374: Test failed: Expected 9, got 8 package.c:7385: Test failed: Expected "E:\\two\", got "E:\two\" package.c:7386: Test failed: Expected 8, got 7 package.c:7397: Test failed: Expected "E:\\four\", got "E:\four\" package.c:7398: Test failed: Expected 9, got 8 package.c:7409: Test failed: Expected "E:\\six\", got "E:\six\" package.c:7410: Test failed: Expected 8, got 7 package.c:7421: Test failed: Expected "E:\\eight\", got "E:\eight\" package.c:7422: Test failed: Expected 10, got 9 package.c:7433: Test failed: Expected "E:\\ten\", got "E:\ten\" package.c:7434: Test failed: Expected 8, got 7 package.c:7445: Test failed: Expected "E:\\twelve\", got "E:\twelve\" package.c:7446: Test failed: Expected 11, got 10 package.c:7497: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7498: Test failed: Expected 10, got 9 package.c:7507: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7508: Test failed: Expected 10, got 9 package.c:7517: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7518: Test failed: Expected 10, got 9 package.c:7529: Test failed: Expected "E:\\one\", got "E:\one\" package.c:7530: Test failed: Expected 8, got 7 package.c:7541: Test failed: Expected "E:\\three\", got "E:\three\" package.c:7542: Test failed: Expected 10, got 9 package.c:7553: Test failed: Expected "E:\\five\", got "E:\five\" package.c:7554: Test failed: Expected 9, got 8 package.c:7565: Test failed: Expected "E:\\seven\", got "E:\seven\" package.c:7566: Test failed: Expected 10, got 9 package.c:7577: Test failed: Expected "E:\\nine\", got "E:\nine\" package.c:7578: Test failed: Expected 9, got 8 package.c:7589: Test failed: Expected "E:\\eleven\", got "E:\eleven\" package.c:7590: Test failed: Expected 11, got 10 package.c:7726: Test failed: Expected "E:\\", got "E:\" package.c:7727: Test failed: Expected 4, got 3 package.c:7738: Test failed: Expected "E:\\", got "E:\" package.c:7739: Test failed: Expected 4, got 3 package.c:7746: Test failed: Expected "E:\\", got "E:\" package.c:7747: Test failed: Expected 4, got 3 package.c:7844: Test failed: Expected "E:\\", got "E:\" package.c:7845: Test failed: Expected 4, got 3 package.c:7852: Test failed: Expected "E:\\", got "E:\" package.c:7853: Test failed: Expected 4, got 3 package.c:7860: Test failed: Expected "E:\\", got "E:\" package.c:7861: Test failed: Expected 4, got 3 package.c:7880: Test failed: Expected "E:\\", got "E:\" package.c:7881: Test failed: Expected 4, got 3 package.c:7888: Test failed: Expected "E:\\", got "E:\" package.c:7889: Test failed: Expected 4, got 3 package.c:7908: Test failed: Expected "E:\\", got "E:\" package.c:7909: Test failed: Expected 4, got 3 package.c:7916: Test failed: Expected "E:\\", got "E:\" package.c:7917: Test failed: Expected 4, got 3 package.c:7936: Test failed: Expected "E:\\", got "E:\" package.c:7937: Test failed: Expected 4, got 3 package.c:7944: Test failed: Expected "E:\\", got "E:\" package.c:7945: Test failed: Expected 4, got 3 === wvistau64 (64 bit package) === package.c:4034: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4040: Test failed: Expected "E:\\FileName2", got "E:\FileName2" package.c:4046: Test failed: Expected "E:\\FileName3", got "E:\FileName3" package.c:4058: Test failed: Expected "E:\\FileName5", got "E:\FileName5" package.c:4064: Test failed: Expected "E:\\", got "E:\" package.c:4070: Test failed: Expected "E:\\", got "E:\" package.c:4086: Test failed: Expected "E:\\FileName8.dll", got "E:\FileName8.dll" package.c:4097: Test failed: Expected "E:\\FileName10.dll", got "E:\FileName10.dll" package.c:4556: Test failed: Expected ERROR_SUCCESS, got 1627 package.c:4648: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4659: Test failed: Expected "E:\\", got "E:\" package.c:4670: Test failed: Expected "E:\\", got "E:\" package.c:4720: Test failed: Expected "E:\\FileName3.dll", got "E:\FileName3.dll" package.c:4731: Test failed: Expected "E:\\FileName5.dll", got "E:\FileName5.dll" package.c:4746: Test failed: Expected "E:\\", got "E:\" package.c:4751: Test failed: Expected "", got "E:\" package.c:4767: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:4776: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:5026: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:5037: Test failed: Expected "E:\\", got "E:\" package.c:5043: Test failed: Expected "E:\\", got "E:\" package.c:5064: Test failed: Expected "E:\\FileName2.dll", got "E:\FileName2.dll" package.c:5075: Test failed: Expected "E:\\FileName4.dll", got "E:\FileName4.dll" package.c:5315: Test failed: Expected "E:\\FileName1", got "E:\FileName1" package.c:5321: Test failed: Expected "E:\\", got "E:\" package.c:5338: Test failed: Expected "E:\\one\two\three\FileName2", got "E:\one\two\three\FileName2" package.c:5349: Test failed: Expected "E:\\one\two\three\FileName2", got "E:\one\two\three\FileName2" package.c:5357: Test failed: Expected "E:\\FileName3.dll", got "E:\FileName3.dll" package.c:5701: Test failed: Expected E:\\winetest-package.msi, got E:\winetest-package.msi package.c:6333: Test failed: Expected E:\\abelisaurus or empty string, got E:\abelisaurus package.c:6357: Test failed: Expected E:\\ or empty string, got E:\ package.c:6401: Test failed: Expected E:\\ or empty string, got E:\ package.c:6410: Test failed: Expected E:\\neosodon\ or empty string, got E:\neosodon\ package.c:6640: Test failed: Expected "E:\\", got "E:\" package.c:6641: Test failed: Expected 4, got 3 package.c:6648: Test failed: Expected "E:\\", got "E:\" package.c:6649: Test failed: Expected 4, got 3 package.c:6665: Test failed: Expected "E:\\", got "E:\" package.c:6666: Test failed: Expected 4, got 3 package.c:6672: Test failed: Expected "E:\\", got "E:\" package.c:6673: Test failed: Expected 4, got 3 package.c:6680: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6681: Test failed: Expected 14, got 13 package.c:6688: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6689: Test failed: Expected 19, got 18 package.c:6699: Test failed: Expected "E:\\", got "E:\" package.c:6700: Test failed: Expected 4, got 3 package.c:6707: Test failed: Expected "E:\\", got "E:\" package.c:6708: Test failed: Expected 4, got 3 package.c:6724: Test failed: Expected "E:\\", got "E:\" package.c:6725: Test failed: Expected 4, got 3 package.c:6731: Test failed: Expected "E:\\", got "E:\" package.c:6732: Test failed: Expected 4, got 3 package.c:6739: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6740: Test failed: Expected 14, got 13 package.c:6747: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6748: Test failed: Expected 19, got 18 package.c:6758: Test failed: Expected "E:\\", got "E:\" package.c:6759: Test failed: Expected 4, got 3 package.c:6766: Test failed: Expected "E:\\", got "E:\" package.c:6767: Test failed: Expected 4, got 3 package.c:6783: Test failed: Expected "E:\\", got "E:\" package.c:6784: Test failed: Expected 4, got 3 package.c:6790: Test failed: Expected "E:\\", got "E:\" package.c:6791: Test failed: Expected 4, got 3 package.c:6798: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6799: Test failed: Expected 14, got 13 package.c:6806: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6807: Test failed: Expected 19, got 18 package.c:6817: Test failed: Expected "E:\\", got "E:\" package.c:6818: Test failed: Expected 4, got 3 package.c:6825: Test failed: Expected "E:\\", got "E:\" package.c:6826: Test failed: Expected 4, got 3 package.c:6842: Test failed: Expected "E:\\", got "E:\" package.c:6843: Test failed: Expected 4, got 3 package.c:6849: Test failed: Expected "E:\\", got "E:\" package.c:6850: Test failed: Expected 4, got 3 package.c:6857: Test failed: Expected "E:\\subsource\", got "E:\subsource\" package.c:6858: Test failed: Expected 14, got 13 package.c:6865: Test failed: Expected "E:\\subsource\sub2\", got "E:\subsource\sub2\" package.c:6866: Test failed: Expected 19, got 18 package.c:6881: Test failed: Expected 4, got 3 package.c:6898: Test failed: Expected 4, got 3 package.c:6904: Test failed: Expected ERROR_MORE_DATA, got 0 package.c:6907: Test failed: Expected 4, got 3 package.c:6914: Test failed: Expected "E:\\", got "E:\" package.c:6915: Test failed: Expected 4, got 3 package.c:6926: Test failed: Expected "E:\\", got "E:\" package.c:6927: Test failed: Expected 4, got 3 package.c:7022: Test failed: Expected "E:\\", got "E:\" package.c:7023: Test failed: Expected 4, got 3 package.c:7030: Test failed: Expected "E:\\", got "E:\" package.c:7031: Test failed: Expected 4, got 3 package.c:7040: Test failed: Expected "E:\\", got "E:\" package.c:7041: Test failed: Expected 4, got 3 package.c:7049: Test failed: Expected "E:\\", got "E:\" package.c:7050: Test failed: Expected 4, got 3 package.c:7056: Test failed: Expected "E:\\", got "E:\" package.c:7057: Test failed: Expected 4, got 3 package.c:7064: Test failed: Expected "E:\\", got "E:\" package.c:7065: Test failed: Expected 4, got 3 package.c:7072: Test failed: Expected "E:\\", got "E:\" package.c:7073: Test failed: Expected 4, got 3 package.c:7083: Test failed: Expected "E:\\", got "E:\" package.c:7084: Test failed: Expected 4, got 3 package.c:7091: Test failed: Expected "E:\\", got "E:\" package.c:7092: Test failed: Expected 4, got 3 package.c:7101: Test failed: Expected "E:\\", got "E:\" package.c:7102: Test failed: Expected 4, got 3 package.c:7110: Test failed: Expected "E:\\", got "E:\" package.c:7111: Test failed: Expected 4, got 3 package.c:7117: Test failed: Expected "E:\\", got "E:\" package.c:7118: Test failed: Expected 4, got 3 package.c:7125: Test failed: Expected "E:\\", got "E:\" package.c:7126: Test failed: Expected 4, got 3 package.c:7133: Test failed: Expected "E:\\", got "E:\" package.c:7134: Test failed: Expected 4, got 3 package.c:7144: Test failed: Expected "E:\\", got "E:\" package.c:7145: Test failed: Expected 4, got 3 package.c:7152: Test failed: Expected "E:\\", got "E:\" package.c:7153: Test failed: Expected 4, got 3 package.c:7162: Test failed: Expected "E:\\", got "E:\" package.c:7163: Test failed: Expected 4, got 3 package.c:7171: Test failed: Expected "E:\\", got "E:\" package.c:7172: Test failed: Expected 4, got 3 package.c:7178: Test failed: Expected "E:\\", got "E:\" package.c:7179: Test failed: Expected 4, got 3 package.c:7186: Test failed: Expected "E:\\", got "E:\" package.c:7187: Test failed: Expected 4, got 3 package.c:7194: Test failed: Expected "E:\\", got "E:\" package.c:7195: Test failed: Expected 4, got 3 package.c:7205: Test failed: Expected "E:\\", got "E:\" package.c:7206: Test failed: Expected 4, got 3 package.c:7213: Test failed: Expected "E:\\", got "E:\" package.c:7214: Test failed: Expected 4, got 3 package.c:7223: Test failed: Expected "E:\\", got "E:\" package.c:7224: Test failed: Expected 4, got 3 package.c:7232: Test failed: Expected "E:\\", got "E:\" package.c:7233: Test failed: Expected 4, got 3 package.c:7239: Test failed: Expected "E:\\", got "E:\" package.c:7240: Test failed: Expected 4, got 3 package.c:7247: Test failed: Expected "E:\\", got "E:\" package.c:7248: Test failed: Expected 4, got 3 package.c:7255: Test failed: Expected "E:\\", got "E:\" package.c:7256: Test failed: Expected 4, got 3 package.c:7353: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7354: Test failed: Expected 9, got 8 package.c:7363: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7364: Test failed: Expected 9, got 8 package.c:7373: Test failed: Expected "E:\\long\", got "E:\long\" package.c:7374: Test failed: Expected 9, got 8 package.c:7385: Test failed: Expected "E:\\two\", got "E:\two\" package.c:7386: Test failed: Expected 8, got 7 package.c:7397: Test failed: Expected "E:\\four\", got "E:\four\" package.c:7398: Test failed: Expected 9, got 8 package.c:7409: Test failed: Expected "E:\\six\", got "E:\six\" package.c:7410: Test failed: Expected 8, got 7 package.c:7421: Test failed: Expected "E:\\eight\", got "E:\eight\" package.c:7422: Test failed: Expected 10, got 9 package.c:7433: Test failed: Expected "E:\\ten\", got "E:\ten\" package.c:7434: Test failed: Expected 8, got 7 package.c:7445: Test failed: Expected "E:\\twelve\", got "E:\twelve\" package.c:7446: Test failed: Expected 11, got 10 package.c:7497: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7498: Test failed: Expected 10, got 9 package.c:7507: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7508: Test failed: Expected 10, got 9 package.c:7517: Test failed: Expected "E:\\short\", got "E:\short\" package.c:7518: Test failed: Expected 10, got 9 package.c:7529: Test failed: Expected "E:\\one\", got "E:\one\" package.c:7530: Test failed: Expected 8, got 7 package.c:7541: Test failed: Expected "E:\\three\", got "E:\three\" package.c:7542: Test failed: Expected 10, got 9 package.c:7553: Test failed: Expected "E:\\five\", got "E:\five\" package.c:7554: Test failed: Expected 9, got 8 package.c:7565: Test failed: Expected "E:\\seven\", got "E:\seven\" package.c:7566: Test failed: Expected 10, got 9 package.c:7577: Test failed: Expected "E:\\nine\", got "E:\nine\" package.c:7578: Test failed: Expected 9, got 8 package.c:7589: Test failed: Expected "E:\\eleven\", got "E:\eleven\" package.c:7590: Test failed: Expected 11, got 10 package.c:7726: Test failed: Expected "E:\\", got "E:\" package.c:7727: Test failed: Expected 4, got 3 package.c:7738: Test failed: Expected "E:\\", got "E:\" package.c:7739: Test failed: Expected 4, got 3 package.c:7746: Test failed: Expected "E:\\", got "E:\" package.c:7747: Test failed: Expected 4, got 3 package.c:7844: Test failed: Expected "E:\\", got "E:\" package.c:7845: Test failed: Expected 4, got 3 package.c:7852: Test failed: Expected "E:\\", got "E:\" package.c:7853: Test failed: Expected 4, got 3 package.c:7860: Test failed: Expected "E:\\", got "E:\" package.c:7861: Test failed: Expected 4, got 3 package.c:7880: Test failed: Expected "E:\\", got "E:\" package.c:7881: Test failed: Expected 4, got 3 package.c:7888: Test failed: Expected "E:\\", got "E:\" package.c:7889: Test failed: Expected 4, got 3 package.c:7908: Test failed: Expected "E:\\", got "E:\" package.c:7909: Test failed: Expected 4, got 3 package.c:7916: Test failed: Expected "E:\\", got "E:\" package.c:7917: Test failed: Expected 4, got 3 package.c:7936: Test failed: Expected "E:\\", got "E:\" package.c:7937: Test failed: Expected 4, got 3 package.c:7944: Test failed: Expected "E:\\", got "E:\" package.c:7945: Test failed: Expected 4, got 3

1 0

Re: [website] German translation for release 1.7.22
by Rico Schüller 24 Jul '14

24 Jul '14

On 16.07.2014 00:24, Julian Rüger wrote: > + <p>Der Quelltext ist ab sofort <a href="http://prdownloads.sourceforge.net/wine/wine-1.7.22.tar.bz2">verfügbar</a>. > +15 Binärpakete werden gerade erstellt und stehen bald auf den jeweiligen <a href="{$root}/download">Downloadseiten</a> zur Verfügung. There is a 15 too much...

2 1

Re: [PATCH] riched20: Implement ITextSelection::GetChar.
by Huw Davies 23 Jul '14

23 Jul '14

On Tue, Jul 22, 2014 at 06:11:07PM +0800, Jactry Zeng wrote: > --- > dlls/riched20/richole.c | 13 +++++++++-- > dlls/riched20/tests/richole.c | 51 > +++++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 62 insertions(+), 2 deletions(-) > Before you start implementing the ITextSelection methods, have you thought about how the ITextRange returned by ITextDocument::GetStoryRanges would work? It seems to me it would be useful to have a text range object that could be used by both, rather than implementing two lots of ITextRange methods. Huw.

2 4

Re: winetest: Consistently use strict and warnings in the main CGI scripts.
by Alexandre Julliard 22 Jul '14

22 Jul '14

Francois Gouget <fgouget(a)codeweavers.com> writes: > diff --git a/winetest/winetest.cgi b/winetest/winetest.cgi > index 8c72e02..61dba49 100755 > --- a/winetest/winetest.cgi > +++ b/winetest/winetest.cgi > @@ -1,4 +1,4 @@ > -#!/usr/bin/perl > +#!/usr/bin/perl -w Any reason for adding this? I thought you wanted to remove them... -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [2/3] msi/tests: Add non-existence value tests for mixed package. (try 2)
by Alexandre Julliard 22 Jul '14

22 Jul '14

Akihiro Sagawa <sagawa.aki(a)gmail.com> writes: > This is part 1 of 2 of retrying `[7/8] msi/tests: Add more registry > tests.' (Patch 105588). > In this try, I divided the previous patch into two pieces because the > test was failed on Alexandre's 64-bit environment due to some uncertain > reason. With this series we can figure out failure points. If part 1 > (this patch) is failed, existing table is broken. Otherwise, additional > entries trigger failures. Of course now it's no longer failing, even with all the patches ;-) -- Alexandre Julliard julliard(a)winehq.org

2 1

imagehlp: Implement (parts of) BindImageEx
by Bernhard Reiter 22 Jul '14

22 Jul '14

Okay, on to the implementation. Grateful for any reviews!

1 0

Re: quartz: Destroy BaseFilter after child class.
by Austin English 21 Jul '14

21 Jul '14

On Mon, Jul 21, 2014 at 12:04 PM, Thomas Faber <thomas.faber(a)reactos.org> wrote: > For the AsyncReader, this is a use after free on the critical section > again. > > The NullRenderer doesn't have any pins, so that change is mostly > cosmetical to align it with the other classes. > > The Parser change fixes a memory leak in addition to the use after free, > because AVISplitter_Release manually decrements the refCount and calls > Parser_Destroy instead of using Parser_Release -- so the filter's > members were never released in this code path. > > > You forgot the patch. Cheers, -Austin

1 0

imagehlp/tests: Add test for BindImageEx
by Bernhard Reiter 21 Jul '14

21 Jul '14

Still struggling to get my first patch ready to be committed. I've removed all the typecasts I was able to, fixed variable names, and tried to initialize variables whereever required, as told by people on #winehackers. Having been told on that channel to only post to wine-patches@ after having the patch reviewed on this list, I'd be grateful for a (hopefully final) review. Bernhard

2 1

Re: [PATCH] vbscript: Implemented IsNumeric(try 2)
by Marvin 21 Jul '14

21 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8046 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [PATCH 1/2] riched20: Implement ITextSelection::GetText. (try 3)
by Huw Davies 21 Jul '14

21 Jul '14

On Thu, Jul 03, 2014 at 04:45:42PM +0800, Jactry Zeng wrote: > index 6f2d579..2553b50 100644 > --- a/dlls/riched20/richole.c > +++ b/dlls/riched20/richole.c > @@ -783,11 +783,31 @@ static HRESULT WINAPI ITextSelection_fnInvoke( > static HRESULT WINAPI ITextSelection_fnGetText(ITextSelection *me, BSTR *pbstr) > { > ITextSelectionImpl *This = impl_from_ITextSelection(me); > + ME_Cursor *start = NULL, *end = NULL; > + int nChars; > + > if (!This->reOle) > return CO_E_RELEASED; > + TRACE("%p\n", pbstr); > + if (!pbstr) > + return E_INVALIDARG; > > - FIXME("not implemented\n"); > - return E_NOTIMPL; > + ME_GetSelection(This->reOle->editor, &start, &end); > + nChars = ME_GetCursorOfs(end) - ME_GetCursorOfs(start); > + if (!nChars) > + { > + *pbstr = NULL; > + return S_OK; > + } > + > + *pbstr = SysAllocStringLen(NULL, nChars); > + if (!*pbstr) > + return E_OUTOFMEMORY; > + /* FIXME: a '\r' should be appended at the end of a story */ > + ME_GetTextW(This->reOle->editor, *pbstr, nChars, start, nChars, 0); Actually, perhaps you could fix the FIXME. GetTextW already has the ability to add \r\n, so extending this to add just \r shouldn't be too difficult. Also, in the tests, you leak the BSTRs. Huw.

2 17

Re: vbscript: Use VariantChangeType in to_int.
by Marvin 21 Jul '14

21 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8043 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [3/3] msi/tests: Add CLSID registry tests for mixed package.
by Marvin 21 Jul '14

21 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8042 Your paranoid android. === w2000pro (32 bit install) === The test timed out === wxppro (32 bit install) === The test timed out === w7u (32 bit install) === The test timed out

1 0

Re: [2/3] msi/tests: Add non-existence value tests for mixed package. (try 2)
by Marvin 21 Jul '14

21 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8041 Your paranoid android. === wxppro (32 bit install) === The test timed out === w7u (32 bit install) === The test timed out

1 0

Re: [PATCH] vbscript: Implemented IsNumeric
by Dmitry Timoshkov 21 Jul '14

21 Jul '14

Shuai Meng <mengshuaicalendr(a)gmail.com> wrote: > + switch(V_VT(arg)) { > + case VT_UI1: > + case VT_I2: > + case VT_I4: > + case VT_I8: > + case VT_R4: > + case VT_R8: > + case VT_BOOL: > + case VT_EMPTY: > + case VT_CY: > + V_BOOL(res) = VARIANT_TRUE; > + break; This list is far from being complete. It seems that it should also contain at least VT_UI2, VT_UI4, VT_UI8, VT_I1, VT_INT, VT_UINT. VT_VECTOR, VT_ARRAY and VT_BYREF modifers probably also should be taken into account. -- Dmitry.

3 6

Re: [PATCH 5/5] ws2_32: Add an interactive test for interface change notifications (resend 2).
by Marvin 18 Jul '14

18 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8031 Your paranoid android. === w7u (32 bit sock) === sock.c:618: Test failed: oob_server (b20): not at the OOB mark: 1

1 0

Re: [2/4] server: Support sending process and thread security descriptors for the "new_process" request in the protocol.
by Alexandre Julliard 17 Jul '14

17 Jul '14

Joris van der Wel <joris(a)jorisvanderwel.com> writes: > + int inherit_all; /* inherit all handles from parent */ > + unsigned int create_flags; /* creation flags */ > + int socket_fd; /* file descriptor for process socket */ > + obj_handle_t exe_file; /* file handle for main exe */ > + unsigned int process_access; /* access rights for process object */ > + unsigned int process_attr; /* attributes for process object */ > + unsigned int thread_access; /* access rights for thread object */ > + unsigned int thread_attr; /* attributes for thread object */ > + cpu_type_t cpu; /* CPU that the new process will use */ > + data_size_t process_sd_size; /* size of the process security descriptor */ > + data_size_t thread_sd_size; /* size of the thread security descriptor */ > + data_size_t info_size; /* size of startup info */ > + data_size_t env_size; /* size of the environment */ > + VARARG(process_sd,security_descriptor,process_sd_size); /* security descriptor to set on the process */ > + VARARG(thread_sd,security_descriptor,thread_sd_size); /* security descriptor to set on the thread */ > + VARARG(info,startup_info,info_size); /* startup information */ > + VARARG(env,unicode_str,env_size); /* environment for new process */ There's no reason to add the environment size. Also you need to validate all the sizes before using them. And please avoid reformatting lines that you are not changing. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH] vbscript: Implemented IsNumeric
by Marvin 17 Jul '14

17 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8022 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [7/8] msi/tests: Add more registry tests.
by Alexandre Julliard 15 Jul '14

15 Jul '14

Akihiro Sagawa <sagawa.aki(a)gmail.com> writes: > --- > dlls/msi/tests/install.c | 90 ++++++++++++++++++++++++++++++++++++++++++++---- > 1 file changed, 83 insertions(+), 7 deletions(-) It doesn't work here on 64-bit: ../../../../wine/tools/runtest -q -P wine -T ../../.. -M msi.dll -p msi_test.exe.so install && touch install.ok install.c:5712: Test failed: value test1 should found, got 2 install.c:5720: Test failed: value test1 shouldn't found install.c:5751: Test failed: 32-bit component key not removed install.c:5754: Test failed: 64-bit component key not removed install.c:5773: Test failed: value test1 should found, got 2 install.c:5781: Test failed: value test1 shouldn't found install.c:5812: Test failed: 32-bit component key not removed install.c:5815: Test failed: 64-bit component key not removed -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [1/9] wined3d: Make the card selection for binary drivers depend only on gl_renderer like it already is for the mesa drivers and remove the gl_info parameter from the select_card callback. (try2)
by Alexandre Julliard 15 Jul '14

15 Jul '14

Andrei Slăvoiu <andrei.slavoiu(a)gmail.com> writes: > --- > dlls/wined3d/directx.c | 568 +++++++++++++++++++++++-------------------------- > 1 file changed, 269 insertions(+), 299 deletions(-) It doesn't work here: ../../../tools/runtest -q -P wine -T ../../.. -M d3d8.dll -p d3d8_test.exe.so device && touch device.ok err:d3d:resource_init Out of adapter memory wine: Unhandled page fault on read access to 0x69766574 at address 0x6862ab1c (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x69766574 in 32-bit code (0x6862ab1c). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:6862ab1c ESP:0032fa50 EBP:0032fb08 EFLAGS:00010202( R- -- I - - - ) EAX:68667f05 EBX:68678e50 ECX:00000000 EDX:69766564 ESI:68667f05 EDI:0032fab8 Stack dump: 0x0032fa50: 68667f05 00000000 00000000 0032fab8 0x0032fa60: 00000000 00000000 00000280 000001e0 0x0032fa70: 00000000 00000000 00000000 00000000 0x0032fa80: 00000000 00000000 00060048 68667229 0x0032fa90: 00139670 68668b04 00139688 0032fab8 0x0032faa0: 00000000 00132818 0032fad8 00134650 Backtrace: =>0 0x6862ab1c test_swapchain+0x28c() [/home/julliard/wine/wine/dlls/d3d8/tests/device.c:261] in d3d8_test (0x0032fb08) 1 0x68644593 func_device+0x832() [/home/julliard/wine/wine/dlls/d3d8/tests/device.c:6461] in d3d8_test (0x0032fd48) 2 0x6862a22f main+0x37e(argc=<is not available>, argv=<is not available>) [/home/julliard/wine/wine/dlls/d3d8/tests/../../../include/wine/test.h:584] in d3d8_test (0x0032fe18) 3 0x68667e20 __wine_spec_exe_entry+0x7f(peb=<couldn't compute location>) [/home/julliard/wine/wine/dlls/winecrt0/exe_entry.c:36] in d3d8_test (0x0032fe58) 4 0x7b85f65c call_process_entry+0xb() in kernel32 (0x0032fe78) 5 0x7b8606a3 start_process+0x62(peb=<couldn't compute location>) [/home/julliard/wine/wine/dlls/kernel32/process.c:1097] in kernel32 (0x0032feb8) 6 0x7bc7fac0 call_thread_func_wrapper+0xb() in ntdll (0x0032fed8) 7 0x7bc82a6d call_thread_func+0x7c(entry=0x7b860640, arg=0x7ffdf000, frame=0x32ffc8) [/home/julliard/wine/wine/dlls/ntdll/signal_i386.c:2630] in ntdll (0x0032ffa8) 8 0x7bc7fa9e call_thread_entry_point+0x11() in ntdll (0x0032ffc8) 9 0x7bc53f0e start_process+0x1d(kernel_start=0x7b860640) [/home/julliard/wine/wine/dlls/ntdll/loader.c:2856] in ntdll (0x0032ffe8) 10 0x680316dd wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 11 0x6803179b wine_switch_to_stack+0x2a(func=0x7bc53ef0, arg=0x7b860640, stack=0x330000) [/home/julliard/wine/wine/libs/wine/port.c:59] in libwine.so.1 (0xff81e868) 12 0x7bc59a09 LdrInitializeThunk+0x238(kernel_start=<couldn't compute location>, unknown2=<couldn't compute location>, unknown3=<couldn't compute location>, unknown4=<couldn't compute location>) [/home/julliard/wine/wine/dlls/ntdll/loader.c:2910] in ntdll (0xff81e8a8) 13 0x7b866ea3 __wine_kernel_init+0xa02() [/home/julliard/wine/wine/dlls/kernel32/process.c:1269] in kernel32 (0xff81f7a8) 14 0x7bc5a903 __wine_process_init+0x192() [/home/julliard/wine/wine/dlls/ntdll/loader.c:3119] in ntdll (0xff81f838) 15 0x6802ede8 wine_init+0x2c7(argc=0x3, argv=0xff81fd74, error="", error_size=0x400) [/home/julliard/wine/wine/libs/wine/loader.c:952] in libwine.so.1 (0xff81f898) 16 0x7bf00d6c main+0x7b(argc=<is not available>, argv=<is not available>) [/home/julliard/wine/wine/loader/main.c:237] in <wine-loader> (0xff81fcd8) 17 0x682518c5 __libc_start_main+0xf4() in libc.so.6 (0x00000000) 0x6862ab1c test_swapchain+0x28c [/home/julliard/wine/wine/dlls/d3d8/tests/device.c:261] in d3d8_test: call *0x10(%edx) 261 hr = IDirect3DSwapChain8_GetBackBuffer(swapchain3, 0, 0, &backbuffer); -- Alexandre Julliard julliard(a)winehq.org

4 10

Re: [PATCH 2/2] vbscript/tests: Added tests for the subtype of TypeName(try 5)
by Marvin 15 Jul '14

15 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8004 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [PATCH 1/2] vbscript: Implemented Abs(try 9)
by Marvin 15 Jul '14

15 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8003 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

1 0

Re: [PATCH 1/6] ddraw: Add validation to SetPriority / GetPriority.
by Henri Verbeet 15 Jul '14

15 Jul '14

On 15 July 2014 16:47, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > -static HRESULT WINAPI ddraw_surface7_SetPriority(IDirectDrawSurface7 *iface, DWORD Priority) > +static HRESULT WINAPI ddraw_surface7_SetPriority(IDirectDrawSurface7 *iface, DWORD priority) > { > struct ddraw_surface *surface = impl_from_IDirectDrawSurface7(iface); > + DWORD managed = DDSCAPS2_TEXTUREMANAGE | DDSCAPS2_D3DTEXTUREMANAGE; > HRESULT hr; > > - TRACE("iface %p, priority %u.\n", iface, Priority); > + TRACE("iface %p, priority %u.\n", iface, priority); > > wined3d_mutex_lock(); > - hr = wined3d_surface_set_priority(surface->wined3d_surface, Priority); > + /* No need to check for offscreen plain surfaces or mipmap sublevels. SetPriority > + * calls on such surfaces segfault on Windows. */ > + if (!(surface->surface_desc.ddsCaps.dwCaps2 & managed)) > + { > + WARN("Called on non-managed texture returning DDERR_INVALIDPARAMS.\n"); > + hr = DDERR_INVALIDPARAMS; > + } > + else > + hr = wined3d_surface_set_priority(surface->wined3d_surface, priority); > wined3d_mutex_unlock(); > > return hr; > } The existing code already had this of course, but note that wined3d_surface_set_priority() returns the previous priority.

1 0

Re: Re: [2/2] ddraw: add dsurface dimension tests, try 11
by Patrick Rudolph 15 Jul '14

15 Jul '14

Hi Henri, thanks for reviewing. >> + /* 6: Test maximum surface height */ >> + {DDSD_CAPS | DDSD_WIDTH | DDSD_HEIGHT, >> DDSCAPS_OFFSCREENPLAIN, 1, 0x10000, DDERR_INVALIDPARAMS}, >> + /* 7: Test maximum surface width */ >> + {DDSD_CAPS | DDSD_WIDTH | DDSD_HEIGHT, >> DDSCAPS_OFFSCREENPLAIN, 0x10000, 1, DDERR_INVALIDPARAMS}, > It would perhaps also be useful to verify that e.g. a 1 by 0xffff > surface actually is allowed. I've not included the tests for DirectDraw surfaces with dimension 1 by 0xffff and 0xffff by 1 as they fail on wine. The surfaces are provided by Opengl textures and the maximum texture size is less than 0xffff. However on Windows these tests pass, if the graphic cards pitch is great enough. Stefan pointed out that on old cards this test might fail. Should I add a separate test for this including a wine_todo ? I guess this won't be fixed any time soon... Regards, Patrick

3 2

Re: [8/8] msi: Avoid Wow6432Node usage in registry table handling.
by Marvin 15 Jul '14

15 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=8000 Your paranoid android. === w2000pro (32 bit install) === The test timed out === wxppro (32 bit install) === The test timed out

1 0

Re: [7/8] msi/tests: Add more registry tests.
by Marvin 15 Jul '14

15 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=7999 Your paranoid android. === wxppro (32 bit install) === The test timed out === w7u (32 bit install) === The test timed out === w8 (32 bit install) === The test timed out

1 0

Re: [PATCH 5/5] d3d8/tests: Get rid of struct nvertex.
by Marvin 15 Jul '14

15 Jul '14

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://testbot.winehq.org/JobDetails.pl?Key=7993 Your paranoid android. === w8 (32 bit device) === device.c:2398: Test failed: Expected foreground window 000B00CA, got 0002004C. device.c:3040: Test failed: Expected wndproc 0x412cf0, got 0x412cf0.

2 1

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