* On Fri, 10 Sep 2010, joerg-cyril.hoe...@t-systems.com wrote:
>
> Now what to do next?
> - uninitialised memory issue?
> - bad MingW or includes on test.winehq?
>
> How do MingW on test.winehq and testbot.winehq differ?
Difference of primary interest would be in the compiler versions and then
Hi,
the subject should read
"Does test.winehq's MingW miscompile winmm:midi tests?"
Here's the summary of Saulius Krazuckas' testing on WinME machines:
- winmm_test.exe midi fails with INVALPARAM on test.winehq.org
(winmm_test.exe extracted from winetest.exe)
+ No failures with a binary compi
Hi,
please excuse the numerous errors in my last message:
>> Likewise, Octavian Voicu's machines saw no failure with the MSVC
It's actually Saulius Krasuckas' machines.
>> binary, but constantly produce red color on testbot.
>When you say "red color on testbot" you mean 'red' on test.winehq.org?
On 09/06/2010 11:02 AM, joerg-cyril.hoe...@t-systems.com wrote:
Hi,
on test.winehq, WinME systems always report 8 rc=MMSYSERR_INVALPARAM
errors. However, when running a MSVC compiled binary (as found in
testbot job #4990), no such error occurs.
Paul Vriens wrote:
I only see those 8 errors wit
Hi,
on test.winehq, WinME systems always report 8 rc=MMSYSERR_INVALPARAM
errors. However, when running a MSVC compiled binary (as found in
testbot job #4990), no such error occurs.
Paul Vriens wrote:
>I only see those 8 errors with the winetest executable from
>test.winehq.org. My own cross-comp
