February 2008 - Wine-Devel - list.winehq.org

Re: War on conformance test suite failures!

by Reece Dunn

On 05/02/2008, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > Am Dienstag, 5. Februar 2008 00:50:55 schrieb Dan Kegel: > > Great progress was made at Wineconf last year on > > getting our test suite closer to always passing on wine, but > > http://test.winehq.org/data/200801301937/#Wine shows > > that, according to the results collected from people who run > > programs/winetest on Wine, twelve DLLs' tests are currently failing. > > (Let alone the test failures on Windows!) > > http://bugs.winehq.org/show_bug.cgi?id=9916 also > > talks about the fact that "make test" shows failures. > This is only half on-topic, but the d3d9:visual test ran on this machine has > some interesting results: > > Vista: Vista-HomePrem-NoUAC > > Do we have any track who reported them? That one is mine, along with Vista-HomePrem-UAC. They are both on the same high-spec recent HP laptop (HP Pavilion DV95000) machine with an NVidia GeForce 8600M GS graphics card. Is there any specific tests/information you need. - Reece

Feb. 5, 2008

winetest experience

by Jeremy White

Okay, so I boldly tried to use winetest with what documentation I could find, and had an...um...interesting time. I created these files: [jertop] cat build.id fcccd9fca605d1d4c462df5c33f4bacf03bdda5f [jertop] cat build.nfo A Large Shovel [jertop] cat tests.url http://www.IDontKnowWhatURLToPutHere.com/ [jertop] did a make dist, and then did: ./winetest -c -t "jw-etch32" It ran, did it's thing, and had one interactive thing (Gecko fussed at me; that's not a Winetest bug afaik). Then when it was all done, it transferred my nearly 1 MB file, and then errored out with: "Unknown build id" So then I looked at the output file, and sure enough, it had a - for build info, not my fancy git id. So I hacked that, put in jwtip, and then ran winetest -s to send my output file through. And then I have a lovely result here: http://test.winehq.org/data/jwtip/ So that's *something* at least. Although I suspect someone will now have to go clean up my mess :-/. So...what's the convention for build.id etc? And why didn't they get set? Cheers, Jeremy

Feb. 5, 2008

Re: War on conformance test suite failures!

by Chris Robinson

On Monday 04 February 2008 04:06:10 pm Stefan Dösinger wrote: > The bit that interests me is the sRGB test result. It shows that the sRGB > correction is applied after the fog, which would allow us to use > GLX_EXT_framebuffer_sRGB for performance improvements if we can find out in > which cases games have to expect that. Currently I only know that Half Life > 2 should fail on this system. This might be the reason: http://msdn2.microsoft.com/en-us/library/bb172583(VS.85).aspx D3DPMISCCAPS_POSTBLENDSRGBCONVERT - Device supports conversion to sRGB after blending. This flag is available in Direct3D 9Ex only.

Feb. 5, 2008

Re: War on conformance test suite failures!

by Jeremy White

> What's the best way to encourage people to fix these problems? > Should we designate some upcoming day, week, or month > as a conformance test bug squishing party? > Should we offer prizes (or at least notoriety) for > the person who does the best job fixing > conformance test suite bugs (as judged by Alexandre > or his designate)? > Or is a simple call to arms enough? I was struck at how willing people were to work on it at Wineconf; I suspect that a call to arms will do it, so long as someone sticks around to pay attention to the results. Of course, the WPF is relatively flush, so we could offer some prizes as well... I was hoping to sound a cry for the use of winetest [1], but was stymied by a lack of documentation around winetest. Cheers, Jeremy [1] http://www.winehq.org/pipermail/wine-devel/2007-October/059846.html

Feb. 5, 2008

Re: War on conformance test suite failures!

by Stefan Dösinger

Am Dienstag, 5. Februar 2008 00:50:55 schrieb Dan Kegel: > Great progress was made at Wineconf last year on > getting our test suite closer to always passing on wine, but > http://test.winehq.org/data/200801301937/#Wine shows > that, according to the results collected from people who run > programs/winetest on Wine, twelve DLLs' tests are currently failing. > (Let alone the test failures on Windows!) > http://bugs.winehq.org/show_bug.cgi?id=9916 also > talks about the fact that "make test" shows failures. This is only half on-topic, but the d3d9:visual test ran on this machine has some interesting results: Vista: Vista-HomePrem-NoUAC Do we have any track who reported them? The bit that interests me is the sRGB test result. It shows that the sRGB correction is applied after the fog, which would allow us to use GLX_EXT_framebuffer_sRGB for performance improvements if we can find out in which cases games have to expect that. Currently I only know that Half Life 2 should fail on this system.

Feb. 5, 2008

War on conformance test suite failures!

by Dan Kegel

Great progress was made at Wineconf last year on getting our test suite closer to always passing on wine, but http://test.winehq.org/data/200801301937/#Wine shows that, according to the results collected from people who run programs/winetest on Wine, twelve DLLs' tests are currently failing. (Let alone the test failures on Windows!) http://bugs.winehq.org/show_bug.cgi?id=9916 also talks about the fact that "make test" shows failures. This situation greatly confuses new developers, who assume that any test failure is somehow their fault. And that's a reasonable assumption, let's make it so! It would make validating a new Wine development environment easy -- it'd be great to be able to say If it doesn't pass "make test" with no errors, something's wrong with the build environment. What's the best way to encourage people to fix these problems? Should we designate some upcoming day, week, or month as a conformance test bug squishing party? Should we offer prizes (or at least notoriety) for the person who does the best job fixing conformance test suite bugs (as judged by Alexandre or his designate)? Or is a simple call to arms enough?

Feb. 4, 2008

Re: running "make test" results in an error

by Stefan Dösinger

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.

Feb. 4, 2008

Re: running "make test" results in an error

by Austin English

On Feb 4, 2008 1:31 PM, Dan Kegel <dank(a)kegel.com> wrote: > Christopher raccoonone at 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 > > Sadly, yes. See http://bugs.winehq.org/show_bug.cgi?id=9916 > > Believe it or not, the situation was much worse five months ago. > At the last Wineconf, Jeremy White got everybody to spend > a whole day just fixing test failures. We could use something > like that again. +1 -Austin

Feb. 4, 2008

Re: winedbg pdb issue - n00b

by Eric Pouech

Michel Jacques a écrit : > Hi. > > I've have setup my debug build (with pdbs) and MSVCRT debug dlls. > > When stopping on a breakpoint with winedbg, I get a stack of calls in winedbg which does not > contains any function info from my dlls or app. I only get hex offset of call within my dll. But > I do see the information for wine sources though, function name + line number. > > What do I need to do so that winedbg can extract info from my pdb? > _NT_SYMBOL_PATH env variable should point to where your pdb files are A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)

Feb. 4, 2008

re: running "make test" results in an error

by Dan Kegel

Christopher raccoonone at 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 Sadly, yes. See http://bugs.winehq.org/show_bug.cgi?id=9916 Believe it or not, the situation was much worse five months ago. At the last Wineconf, Jeremy White got everybody to spend a whole day just fixing test failures. We could use something like that again. > and if so how do I run the rest of the tests? Elementary, my dear Watson. "make -k test". - Dan

Feb. 4, 2008