I tried running "make test" under Ubuntu 7.10, and I just updated to the latest cvs this morning so it's not too old. However, after only running a couple of tests it exited with an error. Is this normal, and if so how do I run the rest of the tests? I attached a log showing which test fails.
Christopher
make[1]: Entering directory `/home/christopher/wine-git/tools' make[1]: `makedep' is up to date. make[1]: Leaving directory `/home/christopher/wine-git/tools' make[1]: Entering directory `/home/christopher/wine-git/dlls' make[2]: Entering directory `/home/christopher/wine-git/dlls/advapi32/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/advapi32/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/advpack/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/advpack/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/browseui/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/browseui/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/cabinet/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/cabinet/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/comcat/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/comcat/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/comctl32/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/comctl32/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/comdlg32/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/comdlg32/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/credui/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/credui/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/crypt32/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/crypt32/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/cryptnet/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/cryptnet/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/d3d8/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/d3d8/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/d3d9/tests' ../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so device.c && touch device.ok fixme:win:EnumDisplayDevicesW ((null),0,0x34f8c0,0x00000000), stub! fixme:d3d:IWineD3DDeviceImpl_CreateAdditionalSwapChain The app requests more than one back buffer, this can't be supported properly. Please configure the application to use double buffering(=1 back buffer) if possible err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed? device.c:753: Test failed: Screen width is 1680 device.c:754: Test failed: Screen height is 1050 err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed? device.c:798: Test failed: Screen width is 1680 device.c:799: Test failed: Screen height is 1050 err:d3d:IWineD3DDeviceImpl_DrawIndexedPrimitive (0x144548) : Called without a valid index buffer set, returning WINED3DERR_INVALIDCALL fixme:d3d:SetupForBlit >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glOrtho @ context.c / 622 fixme:d3d_surface:flush_to_framebuffer_drawpixels >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glDrawPixels @ surface.c / 1061 fixme:d3d:transform_projection >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glOrtho @ state.c / 2802 fixme:d3d_surface:flush_to_framebuffer_drawpixels >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glDrawPixels @ surface.c / 1061 fixme:d3d:IWineD3DDeviceImpl_SetLightEnable Too many concurrently active lights make[2]: *** [device.ok] Error 4 make[2]: Leaving directory `/home/christopher/wine-git/dlls/d3d9/tests' make[1]: *** [d3d9/tests/__test__] Error 2 make[1]: Leaving directory `/home/christopher/wine-git/dlls' make: *** [dlls/__test__] Error 2
On 04/02/2008, Christopher raccoonone@procyongames.com wrote:
I tried running "make test" under Ubuntu 7.10, and I just updated to the latest cvs this morning so it's not too old. However, after only running a couple of tests it exited with an error. Is this normal, and if so how do I run the rest of the tests? I attached a log showing which test fails.
You can check the state of the tests at http://test.winehq.org/data/200801301937/. I also get test failures on Ubuntu 7.10, so this is normal, even though it is undesirable.
You can run make -k test (the -k tells make to continue on error).
What I do is:
make -k test | tee results.log cat results.log | grep -F Error
- Reece
Am Montag, 4. Februar 2008 18:41:23 schrieb Christopher:
err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed? device.c:753: Test failed: Screen width is 1680 device.c:754: Test failed: Screen height is 1050
That is causing the tests to fail. I've never seen that specific behavior before, but I think that winex11 doesn't return an error if the resolution change fails. This is because some users have "broken" X11 setups which only support one resolution. That way games run in a corner of the screen instead of bailing out.
The consequence is that the test isn't told that the resolution switch failed, and then complains about an unexpected resolution.
I think the problem with the test is that it assumes that 640x480 is available. I haven't seen a Windows box yet where this wasn't the case, but I think the best option is to check for that and skip the test with a warning to avoid failing make test.
Obviously, games that require 640x480 will have issues on your computer as well.
Stefan Dösinger stefan@codeweavers.com writes:
Am Montag, 4. Februar 2008 18:41:23 schrieb Christopher:
err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed? device.c:753: Test failed: Screen width is 1680 device.c:754: Test failed: Screen height is 1050
That is causing the tests to fail. I've never seen that specific behavior before, but I think that winex11 doesn't return an error if the resolution change fails. This is because some users have "broken" X11 setups which only support one resolution. That way games run in a corner of the screen instead of bailing out.
The usual cause for this failure is an Xrandr bug, the timestamp checking is broken WRT wraparound. If you wait a few days (or restart your X server) it will work again.