September 2011 - Wine-Devel

[RFC] Re: [PATCH 1/2]rpcrt4/tests: Add some commented tests for widl
by Jérôme Gardou Sept. 14, 2011

Sept. 14, 2011

Hello. I've seen that this patch is in "pending" state, and I would like to know what is the problem with it. Also, if commenting the tests isn't a policy you want to enforce (that I would understand), I'm ready to skip them on wine, but how to? Those tests were made with midl from Visual Studio 10, with or without /Os option, and ran smoothly. http://www.winehq.org/pipermail/wine-patches/2011-August/106200.html Regards. Jérôme. Le 06/09/2011 00:50, Jérôme Gardou a écrit : > Also, the added function which seems to be useless permits to detect > the problem that the next patch fixes. > Enable -Oif, and the test of server.c line 947 (after patch > application) will fail. > --- > dlls/rpcrt4/tests/server.c | 46 > ++++++++++++++++++++++++++++++++++++++++++ > dlls/rpcrt4/tests/server.idl | 1 + > 2 files changed, 47 insertions(+), 0 deletions(-) > > > > >

2 1

quartz: Fix converting between the media time and REFTIME
by Joerg-Cyril.Hoehle＠t-systems.com Sept. 14, 2011

Sept. 14, 2011

Hi, I've never tried to understand quartz, but I'd like to know whether quartz expects particular behaviour from the underlying winmm or mmdevapi time/position/length functions. For instance, quartz says its clocks are monotically increasing, whereas no such requirement is documented (or at least known to me) for the audio stream positions. This may seem obvious, but then I came across some mailing list where people reported a sudden backward change in stream position when pluggin/unplugging earphones or the like. Is quartz very decoupled from the underlying audio information? Who stops the clock (if at all) while the stream is paused? BTW, in theory I have the tools to easily test quartz, using my interactive MCI shell http://bugs.winehq.org/show_bug.cgi?id=20232#c10 However every time I tried, I found mciqtz too underpowered to be able to reasonably use it. :-( Using the MCI to use mciqtz (which in turn uses quartz.dll) goes as follows: wine wintest.exe mcishell open foo.wav alias w type mpegvideo status w length play w from 0 notify wait close w # lots of other commands are available open foo.avi alias a type mpegvideo window a state show status a length play a from 0 close a Omit the "type mpegvideo" and mciwave or mciavi will be used instead of mciqtz32.dll Regards, Jörg Höhle

3 2

re: [PATCH 11/21] vbscript: Added function parser implementation
by Dan Kegel Sept. 14, 2011

Sept. 14, 2011

Fails tests reliably (4 out of 4 runs) here under WINEDEBUG=warn+heap on a q9300 (but not on 32 or 64 bit non-warn-heap runs on q9300 or i7). On Wed, Sep 14, 2011 at 7:17 AM, <buildbot(a)kegel.com> wrote: > This is an experimental automated build and test service. > Please feel free to ignore this email while we work the kinks out. > > For more info about this message, see http://wiki.winehq.org/BuildBot > > The Buildbot has detected a failed build on builder runtests-heaptest while building Wine. > Full details are available at: http://buildbot.kegel.com/builders/runtests-heaptest/builds/35 (though maybe not for long, as I'm still reinstalling the buildbot periodically while experimenting) > BUILD FAILED: failed shell_3 > > Errors: > vbscript.c:443: Test failed: expected OnEnterScript > vbscript.c:444: Test failed: expected OnLeaveScript > make: *** [vbscript.ok] Error 2 > >

2 2

Re: [PATCH 1/3] server: certain access flags are illegal for OpenMutex
by Marvin Sept. 14, 2011

Sept. 14, 2011

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=14233 Your paranoid android. === WNT4WSSP6 (32 bit sync) === sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5 === W2KPROSP4 (32 bit sync) === sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5 === WXPPROSP3 (32 bit sync) === sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5 === W2K3R2SESP2 (32 bit sync) === sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5 === WVISTAADM (32 bit sync) === sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5 === W2K8SE (32 bit sync) === sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5 === W7PRO (32 bit sync) === sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5 === W7PROX64 (32 bit sync) === sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5 === W7PROX64 (64 bit sync) === sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5

1 0

Re: [PATCH 06/21] vbscript: Added function arguments compiler implementation
by Octavian Voicu Sept. 14, 2011

Sept. 14, 2011

On Wed, Sep 14, 2011 at 1:56 PM, Jacek Caban <jacek(a)codeweavers.com> wrote: > --- a/dlls/vbscript/compile.c > +++ b/dlls/vbscript/compile.c > @@ -658,9 +658,26 @@ static HRESULT create_function(compile_ctx_t *ctx, function_decl_t *decl, functi > func->code_ctx = ctx->code; > func->type = decl->type; > > + func->arg_cnt = 0; > if(decl->args) { ... > + }else { > + decl->args = NULL; I think you want to set func->args to NULL at the last line. Cheers, Octavian

2 1

Re: [PATCH 19/21] vbscript: Added interp_xor implementation
by Marvin Sept. 14, 2011

Sept. 14, 2011

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=14230 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found

1 0

Re: [PATCH 10/21] vbscript: Added support for sub local variables
by Marvin Sept. 14, 2011

Sept. 14, 2011

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=14224 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found

1 0

Re: [PATCH 09/21] vbscript: Added exit sub statement implementation
by Marvin Sept. 14, 2011

Sept. 14, 2011

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=14223 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found

1 0

Re: [PATCH 08/21] vbscript: Added sub argument tests
by Marvin Sept. 14, 2011

Sept. 14, 2011

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=14222 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found

1 0

Re: [PATCH 02/21] vbscript: Added function compiler implementation
by Marvin Sept. 14, 2011

Sept. 14, 2011

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=14220 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found

2 1