Re: Fix the winmm/wave tests

[Alexandre Julliard]

Francois Gouget <fgouget(a)free.fr> writes:
> * dlls/winmm/tests/wave.c
>
> Error handling in waveOutOpen works now (patch has been in CVs for a
> couple of weeks) -> removing the todo_wine

This doesn't work for me:

../../../tools/runtest -q -P wine -M winmm.dll -T ../../.. -p winmm_test.exe.so wave.c && touch wave.ok
err:wave:wodOpen Rate doesn't match (requested 2000000 Hz, got 48000 Hz)
err:wave:wodOpen Rate doesn't match (requested 2000000 Hz, got 48000 Hz)
wave.c:145: Test failed: opening the device at 2MHz should fail 0: rc=4

-- 
Alexandre Julliard
julliard(a)winehq.com

Fix the winmm/wave tests

[Francois Gouget]

On 6 Dec 2002, Alexandre Julliard wrote:
> Francois Gouget <fgouget(a)free.fr> writes:
> > * dlls/winmm/tests/wave.c
> >
> > Error handling in waveOutOpen works now (patch has been in CVs for a
> > couple of weeks) -> removing the todo_wine
>
> This doesn't work for me:
>
> ../../../tools/runtest -q -P wine -M winmm.dll -T ../../.. -p winmm_test.exe.so wave.c && touch wave.ok
> err:wave:wodOpen Rate doesn't match (requested 2000000 Hz, got 48000 Hz)
> err:wave:wodOpen Rate doesn't match (requested 2000000 Hz, got 48000 Hz)
> wave.c:145: Test failed: opening the device at 2MHz should fail 0: rc=4

Strange. 4 means MMSYSERR_ALLOCATED and it appears that it may be
returned if a Unix process already is using the device or if the device
really is already allocated by Wine.

I guess it's reproducible? Was another process using the sound device at
the time? Are you using the wineoss driver or are you using one of the
new ones?


-- 
Francois Gouget         fgouget(a)free.fr        http://fgouget.free.fr/
 The greatest programming project of all took six days; on the seventh day the
  programmer rested. We've been trying to debug the *&^%$#@ thing ever since.
                      Moral: design before you implement.