http://bugs.winehq.org/show_bug.cgi?id=19495
robertgonder@embarqmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #15 from robertgonder@embarqmail.com 2009-08-04 22:27:34 --- (In reply to comment #12)
maybe someone should have point you to: http://wiki.winehq.org/ConformanceTests
"How to run conformance tests." Seems to tell me (not very well) how to download and run a test exe. It says nothing about adding a new test.
OTOH, your link takes me one step deeper to http://wiki.winehq.org/MakeTestFailures Where it says I shouldn't even try to do what you-all are asking: "(Note: building Wine on 64 bit systems can be difficult. If you have a 64 bit system, and you haven't already successfully built wine, please don't try just to help out with this, it's too much trouble.)"
and how to get the source of wine where "dlls/user32/tests/dialog.c" is located: http://wiki.winehq.org/GitWine
"Using Git to maintain your patches against Wine" I suppose that means I use git to get the test code? I'm not much interested in recompiling wine or patching it. Or in learning how to use git. I'm a one-man shop. User tells me about a bug, I go in and fix it. I don't ask the user to learn programming and git and then write a conformance test for me.
I followed all 6 steps on the Bugzilla page, and then filed a detailed bug report including steps to reproduce the bug. I've provided two codes, the first one a complete executable, demonstrating the bug. The second, the nearest I could make out, a conformance test to be added into the dialog test by the keepers of the test. I guess no one has bothered to run the first full executable or this wouldn't still be "unconfirmed".
I've done my job, twice over. I've coded around your bug. Commercial software probably doesn't code around it, so I figure it might be causing problems that you haven't figured out yet. I can't do your job for you. But I can point out failings as they come up.
I am truly sorry the Wine Bug Whackers aren't interested in knowing about actual bugs.