http://bugs.winehq.org/show_bug.cgi?id=12142
--- Comment #5 from Brad Martin wine@fatlxception.no-ip.org 2008-03-22 13:57:30 --- (In reply to comment #4)
What are you trying to fix that requires running user32 message tests? Anyway, having the same set of tests failing in the same fashion before and after your patch is a good start.
Nothing specifically yet, I just wanted to get a baseline for the project as a whole before I started changing anything. I thought make test was intended to be a project-wide regression test, so I tried using it for that purpose. When I got failures I asked on IRC whether make test was expected to pass or not, and I was told yes, and to report any failures as bugs. If make test is only intended to be used by one person then disregard; however this diminishes the potential usefulness of the test suite IMO. In the meantime I can patch up my local git branch to pass the tests I expect to pass, but that doesn't prevent someone else from asking the same questions in the future. Seems like it would be helpful to explain this somewhere, as well as things like don't run make test on the ALSA driver (dsound fails), or with any serial ports enabled on your computer (kernel32 fails). I don't see any of this in the Developer's Guide section on make test; is there somewhere else I should be looking?