Hi,
>What behavior do you think Wine is going to do wrong
Matthew van Eerde's web log has a sample silence playing
application using EVENTCALLBACK mode.
http://blogs.msdn.com/b/matthew_van_eerde/archive/2008/12/10/sample-playing…
Running it in Wine shows that Wine violates the assumption/invariant/guarantee IMHO
Event signaled => there's room in the buffer
-- much like winmm's MOM_DONE signals that a buffer is free.
I don't know when the first event is signaled nor at what rate they are signaled.
(Perhaps one is signaled every time one of the mixer's 10ms chunks is processed?).
The app immediately complains and exits.
Wine's mmdevapi current unconditional and periodic SetEvent does not match
the above program's expectations (nor would it match exclusive mode behaviour:
event => complete buffer free for writing). A periodic 10ms event may be fine when
playing goes smooth, but that's not the case right at the beginning, esp. when
filling the buffer before calling Start.
I should turn that into a distinct bug report.
Regards,
Jörg Höhle
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=11553
Your paranoid android.
=== WINEBUILD (build) ===
Patch failed to apply
On Tuesday 07 June 2011 19:44:49 Henri Verbeet wrote:
> if (wined3d_settings.logo)
> - IWineD3DDeviceImpl_LoadLogo(device, wined3d_settings.logo);
> + device_load_logo(device, wined3d_settings.logo);
Does the logo stuff still work? I thought about removing it, I don't think it
has any use.
The original intentions were for debugging(Is wined3d used on Windows?) and
for making nice and fancy screenshots, but I don't think anyone uses it.
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=11551
Your paranoid android.
=== W7PROX64 (64 bit msg) ===
Timeout
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=11550
Your paranoid android.
=== W7PROX64 (64 bit msg) ===
Timeout
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=11549
Your paranoid android.
=== W7PROX64 (64 bit msg) ===
Timeout
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=11548
Your paranoid android.
=== W7PROX64 (64 bit msg) ===
Timeout
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=11547
Your paranoid android.
=== W7PROX64 (64 bit msg) ===
Timeout
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=11546
Your paranoid android.
=== W7PROX64 (64 bit msg) ===
Timeout
Hi,
I have a problem about testing wine where specific to locales (or ANSI
code pages). Because test bots don't seem to test wine in non-English
locales. I'd like to get wine's test results in various locale
environments from test.winehq.org.
Firstly, as a wine intended to handle locale properly, all tests should
succeed in any locales. We could discover locale-depended failure in
other locales. Secondly, if I add a locale specific test, it easy to
prove the issue to others.
In my opinion, adding Russian, Japanese and Chinese would be better.
They are tested by existing XP bots. So how about adding non-English
wine environments to the testbot farm?
--
Best Regards,
Akihiro Sagawa