Re: [7/7] msvcrt/test: Add some simple _vsnwprintf_s tests. (try 2)

On Sun, Jun 6, 2010 at 11:44 PM, Alexander Scott-Johns wrote: > On 7 June 2010 05:39, Austin English wrote: >> On Sun, Jun 6, 2010 at 11:36 PM, Alexander Scott-Johns >> wrote: >>> try 2: todo_wines removed since _vsnwprintf_s is fixed by patch 5. >> >> The todo_wine's need to be removed in the s

Re: [7/7] msvcrt/test: Add some simple _vsnwprintf_s tests. (try 2)

On 7 June 2010 05:39, Austin English wrote: > On Sun, Jun 6, 2010 at 11:36 PM, Alexander Scott-Johns > wrote: >> try 2: todo_wines removed since _vsnwprintf_s is fixed by patch 5. > > The todo_wine's need to be removed in the same patch in which they are > fixed, otherwise, the tests will "fail".

Re: [7/7] msvcrt/test: Add some simple _vsnwprintf_s tests. (try 2)

On Sun, Jun 6, 2010 at 11:36 PM, Alexander Scott-Johns wrote: > try 2: todo_wines removed since _vsnwprintf_s is fixed by patch 5. The todo_wine's need to be removed in the same patch in which they are fixed, otherwise, the tests will "fail". -- -Austin

Re: configure.ac: when checking for ALSA, look for snd_pcm_recover() instead of snd_pcm_hw_params_get_access()

Hello, On 06-06-10 21:09, Austin English wrote: On Sun, Jun 6, 2010 at 3:27 AM, Andrew Nguyen wrote: On Sun, Jun 6, 2010 at 2:50 AM, Austin English wrote: See http://bugs.winehq.org/show_bug.cgi?id=23003 -- -Austin You should probably drop the snd_pcm_hw_params_get_ac

Re: configure.ac: when checking for ALSA, look for snd_pcm_recover() instead of snd_pcm_hw_params_get_access() (try 2)

I hate to nitpick once more, but there are a few things I noticed. My alsa-lib tells me: include/pcm.h:int snd_pcm_recover(snd_pcm_t *pcm, int err, int silent); Therefore, the statement "int ret = snd_pcm_recover(NULL, NULL, NULL);" is somewhat incorrect. Secondly, I think it should be sufficient

Re: configure.ac: when checking for ALSA, look for snd_pcm_recover() instead of snd_pcm_hw_params_get_access() (try 2)

On Sun, Jun 06, 2010 at 02:21:33PM -0500, Austin English wrote: > -- > -Austin > diff --git a/configure.ac b/configure.ac > index 21c0203..46ac100 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -dnl Process this file with autoconf to produce a configure script. > +/dnl Proce

Re: configure.ac: when checking for ALSA, look for snd_pcm_recover() instead of snd_pcm_hw_params_get_access()

On Sun, Jun 6, 2010 at 3:27 AM, Andrew Nguyen wrote: > On Sun, Jun 6, 2010 at 2:50 AM, Austin English > wrote: >> See http://bugs.winehq.org/show_bug.cgi?id=23003 >> >> -- >> -Austin >> >> >> >> > > You should probably drop the snd_pcm_hw_params_get_access argument > check, both because it's not

Re: Running tests on wine

2010/6/6 Nikolay Sivov: You're running it with make, and a test results are from winetest runs. As I remember winetest runs it as 'wine oleaut32_tests.exe typelib' with some env variable to set a platform (this will enable todos output, AFAIK). You're right. I noticed this file but I prefered do

Re: Gecko64 status

Hi Juan, On 6/6/10 7:35 PM, Juan Lang wrote: Any comments and suggestions are welcomed. One suggestion is that bugs get logged about test failures on Wine wherever possible. Dan has done that for the chromium test suite, and that's led to several bugs getting converted to Wine regression

Re: Running tests on wine

2010/6/6 Nikolay Sivov : > On 6/6/2010 21:03, GOUJON Alexandre wrote: >> >> Hi, >> >> I would like to do some (typelib) tests on wine. >> >> So I followed the instructions at >> http://www.winehq.org/docs/winedev-guide/testing-wine >> ( cd dlls/oleaut32/tests/ ; rm typelib.ok && make typelib.ok in

Re: Gecko64 status

Hi Jacek, > However, it doesn't mean that nothing is going on around Wine Gecko. I've > recently switched to mingw-w64 for 32-bit builds. I've very pleased with it. > They are far better in co-operation, don't have senseless politics like > mingw and their quality of headers and libraries is far b

Re: Running tests on wine

On 6/6/2010 21:03, GOUJON Alexandre wrote: Hi, I would like to do some (typelib) tests on wine. So I followed the instructions at http://www.winehq.org/docs/winedev-guide/testing-wine ( cd dlls/oleaut32/tests/ ; rm typelib.ok && make typelib.ok in my case) but I have err's and fixme's wherea

Running tests on wine

Hi, I would like to do some (typelib) tests on wine. So I followed the instructions at http://www.winehq.org/docs/winedev-guide/testing-wine ( cd dlls/oleaut32/tests/ ; rm typelib.ok && make typelib.ok in my case) but I have err's and fixme's whereas the output on wineTestBot is quite differ

Re: xrender.c is does not find fontconfig.h on OS X Tiger

Mike Kronenberg wrote: Dear List OS X Tiger does has not have fontconfig, so I'm building it in ~/buildwine/usr to keep it out of /usr. I include the headers and libs from ~/buildwine/usr with CPPFLAGS and CFLAGS. What Mike meant to say is that MacOSX does not include fontconfig functionality

Re: [PATCH 3/3] shlwapi: Implement SHSetIniStringW

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=2490 Your paranoid android.

Re: [PATCH 2/3] shlwapi: Implement SHGetIniStringW

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=2489 Your paranoid android.

Re: [PATCH 1/3] shlwapi: Be less strict on which type of IShellFolder can be enumerated

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=2488 Your paranoid android.

Re: appwiz: Add the Polish translation

Hey Łukasz, all your translations are written in UTF-8, but to actually use UTF-8, you also have to include a #pragma code_page(65001) on top of the file. In this case for example +#include "res.h" + +LANGUAGE LANG_POLISH, SUBLANG_DEFAULT + +#pragma code_page(65001) Atm, if you compile win

Re: Release plans

> > 340 regressions<-- release announcement > > 356 regressions<-- release announcement + 1week > > 339 regressions<-- release announcement + 2weeks(rc1) > > > 322 regressions<-- release announcement + 3weeks(rc2) > > > 325 regressions<-- release announcement + 4weeks > > As we didn't have a relea

Re: Release plans

On 06/06/2010 11:34 AM, wy...@volny.cz wrote: Hi, another week and Sunday gone so time for simple numbers... 340 regressions<-- release announcement 356 regressions<-- release announcement + 1week 339 regressions<-- release announcement + 2weeks(rc1) 322 regressions<-- release announcement + 3w

Re: Release plans

Hi, another week and Sunday gone so time for simple numbers... 340 regressions <-- release announcement 356 regressions <-- release announcement + 1week 339 regressions <-- release announcement + 2weeks(rc1) 322 regressions <-- release announcement + 3weeks(rc2) 325 regressions <-- release announ

Re: configure.ac: when checking for ALSA, look for snd_pcm_recover() instead of snd_pcm_hw_params_get_access()

On Sun, Jun 6, 2010 at 2:50 AM, Austin English wrote: > See http://bugs.winehq.org/show_bug.cgi?id=23003 > > -- > -Austin > > > > You should probably drop the snd_pcm_hw_params_get_access argument check, both because it's not the function that's being tested, and because, as far as I can tell fro