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=14562
Your paranoid android
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=14554
Your paranoid android
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=14548
Your paranoid android
On 09/26/2011 09:10 AM, Andrew Eikum wrote:
On Mon, Sep 26, 2011 at 04:50:22PM +0200, joerg-cyril.hoe...@t-systems.com
wrote:
I'm not satisfied with the removal of the audio tree from winecfg.
Beside allowing to switch or disable drivers, one key feature was to
allow inspecting the devices that
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=14540
Your paranoid android
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=14533
Your paranoid android
Andrew Eikum writes:
> @@ -84,10 +84,11 @@ END
>
> STRINGTABLE
> BEGIN
> -IDS_ACCEL_FULL "Full"
> -IDS_ACCEL_STANDARD "Standard"
> -IDS_ACCEL_BASIC "Basic"
> -IDS_ACCEL_EMULATION "Emulation"
> +IDS_AUDIO_REG_SETTING "Registry drive
Hey Joerg,
On 09/26/2011 02:57 PM, joerg-cyril.hoe...@t-systems.com wrote:
> Hi,
>
> I've had a glance at the OSS4 mmdevapi logs attached to bug #28056.
> Among others, it appears that every renderer iteration takes way too
> much time. One possible explanation is that OSS write() takes a lot
> o
Fails to apply here. (Requires fuzz, which Alexandre says is verboten.)
-- Forwarded message --
From:
Date: Mon, Sep 26, 2011 at 2:35 AM
Subject: Re: 79321: winmm: waveOutReset returns all buffers.
To: d...@kegel.com, wine-tests-resu...@winehq.org
This is an experimental autom
On Mon, Sep 26, 2011 at 11:14 AM, Michael Stefaniuc wrote:
> Also when Alexandre does "git am" the patch it will fail too.
I just asked Alexandre, and he agrees with you that buildbot should
reject patches that require fuzz.
On 09/26/2011 06:32 PM, Dan Kegel wrote:
> On Mon, Sep 26, 2011 at 2:59 AM, Jerome Leclanche wrote:
>> On Mon, Sep 26, 2011 at 8:46 AM, Francois Gouget wrote:
>>> On Sun, 25 Sep 2011, Dan Kegel wrote:
Patch fails to apply here?
error: patch failed: po/ko.po:11305
error: po/ko.
On Mon, Sep 26, 2011 at 2:59 AM, Jerome Leclanche wrote:
> On Mon, Sep 26, 2011 at 8:46 AM, Francois Gouget wrote:
>> On Sun, 25 Sep 2011, Dan Kegel wrote:
>>> Patch fails to apply here?
>>>
>>> error: patch failed: po/ko.po:11305
>>> error: po/ko.po: patch does not apply
>>
>> That's strange. Th
On Mon, Sep 26, 2011 at 1:20 AM, Francois Gouget wrote:
>> http://kegel.com/wine/loop-fail.sh.txt
>> overnight on the hardware you plan to bring, and
>> email me the results? It creates a log file
>> loop-fails.log which lists each test failure and
>> how many loops it took to get there.
>
> I
Dmitry Timoshkov writes:
> +static void test_VirtualProtect(void)
> +{
> +static const struct test_data
> +{
> +DWORD prot_set, prot_get;
> +} td[] =
> +{
> +{ PAGE_NOACCESS, PAGE_NOACCESS },
> +{ PAGE_READONLY, PAGE_READONLY },
> +{ PAGE_READWRITE,
On Mon, Sep 26, 2011 at 05:05:28PM +0200, joerg-cyril.hoe...@t-systems.com
wrote:
> I agree that dsound -> winmm -> mmdevapi is an abomination.
>
> However, this all goes too fast for me.
> We don't have a fool-proof mmdevapi yet (neither ALSA, nor OSS, nor
> CoreAudio).
> We don't have a bug-fr
Hi,
I agree that dsound -> winmm -> mmdevapi is an abomination.
However, this all goes too fast for me.
We don't have a fool-proof mmdevapi yet (neither ALSA, nor OSS, nor CoreAudio).
We don't have a bug-free winmm->mmdevapi yet.
Since June, I've done nothing than analyse code and fix bugs to he
On Mon, Sep 26, 2011 at 04:50:22PM +0200, joerg-cyril.hoe...@t-systems.com
wrote:
> I'm not satisfied with the removal of the audio tree from winecfg.
> Beside allowing to switch or disable drivers, one key feature was to
> allow inspecting the devices that winmm found on this system.
The goal of
Hi,
I'm not satisfied with the removal of the audio tree from winecfg.
Beside allowing to switch or disable drivers, one key feature was to
allow inspecting the devices that winmm found on this system.
For instance, I've not yet had time to report a bug that since
wine-1.3.25, one such entry show
Hi,
I've had a glance at the OSS4 mmdevapi logs attached to bug #28056.
Among others, it appears that every renderer iteration takes way too
much time. One possible explanation is that OSS write() takes a lot
of time to return, presumably in an attempt to write more than what's
possible without b
On 26/09/2011 3:07 PM, Peter Wilson wrote:
> Hi,
>
> Quick question, might be silly, but is there a version of Wine that can be
> installed on windows or linux to create apps for Mac?
>
> I just want to keep my mac clean and try run things in a dev environment, and
> apple are always so polite
Hi,
Quick question, might be silly, but is there a version of Wine that can be
installed on windows or linux to create apps for Mac?
I just want to keep my mac clean and try run things in a dev environment, and
apple are always so polite to make visualization a pain…
Thank you very much for yo
Sounds like encoding/charset issues. Dan, is buildbot's the same as
the file and/or patch?
On Mon, Sep 26, 2011 at 8:46 AM, Francois Gouget wrote:
> On Sun, 25 Sep 2011, Dan Kegel wrote:
>
>> Patch fails to apply here?
>>
>> error: patch failed: po/ko.po:11305
>> error: po/ko.po: patch does not a
On Fri, 23 Sep 2011, Dan Kegel wrote:
> ... could you run
>http://kegel.com/wine/loop-fail.sh.txt
> overnight on the hardware you plan to bring, and
> email me the results? It creates a log file
> loop-fails.log which lists each test failure and
> how many loops it took to get there.
If the
On Sun, 25 Sep 2011, Dan Kegel wrote:
> Patch fails to apply here?
>
> error: patch failed: po/ko.po:11305
> error: po/ko.po: patch does not apply
That's strange. The patch attached to the email I received on
wine-patches applies fine on a pristine tree here.
--
Francois Gouget
24 matches
Mail list logo
