1. Why are all the archived posts to wine-test-results empty? See http://www.winehq.org/hypermail/wine-tests-results/2004/11 Every message body is empty! What's up with that?
2. The URL http://test.winehq.org/data/ appears to contain digests of all winetest results received by the server, but this information is not documented anywhere I could find at www.winehq.org. Seems like a top level page is in order.
3. winetest.exe currently assumes you're running under Windows. See main.c line 577: (putenv ("WINETEST_PLATFORM=windows") || Wouldn't it be useful to allow Linux results to be computed and reported via winetest, too? Presumably it could detect that it's running on Linux somehow. (perhaps by running uname -a...)
- Dan
On Sun, Nov 07, 2004 at 02:01:13PM -0800, Dan Kegel wrote:
- Why are all the archived posts to wine-test-results empty?
See http://www.winehq.org/hypermail/wine-tests-results/2004/11 Every message body is empty! What's up with that?
That's a good question. Chris, what's going on?
- The URL http://test.winehq.org/data/ appears to contain
digests of all winetest results received by the server, but this information is not documented anywhere I could find at www.winehq.org. Seems like a top level page is in order.
Yes, one is planned for (Under http://www.winehq.org/site/status in the right-hand box), but nobody did it until now. It need to contain: -- an explanation for the entire winetest business -- ditto for winrash (http://winrash.sf.net) -- where they can download them -- how they can help by actually running them (winrash is preferred) -- a legend for the test pages
Any volunteers? :)
- winetest.exe currently assumes you're running under Windows.
See main.c line 577: (putenv ("WINETEST_PLATFORM=windows") || Wouldn't it be useful to allow Linux results to be computed and reported via winetest, too? Presumably it could detect that it's running on Linux somehow. (perhaps by running uname -a...)
It would be cool (and we support it), but in practical terms, it will be more of a problem (that's why we explicitely disable it). We know that all tests run under Wine/Linux anyway, so it would provide little additional benefit, but the potential to screw up our reports is rather large.
Dimitrie O. Paun wrote:
- winetest.exe currently assumes you're running under Windows.
See main.c line 577: (putenv ("WINETEST_PLATFORM=windows") || Wouldn't it be useful to allow Linux results to be computed and reported via winetest, too? Presumably it could detect that it's running on Linux somehow. (perhaps by running uname -a...)
It would be cool (and we support it), but in practical terms, it will be more of a problem (that's why we explicitely disable it). We know that all tests run under Wine/Linux anyway, so it would provide little additional benefit, but the potential to screw up our reports is rather large.
Ah, but you don't disable it, as far as I can tell. As of last month, I was able to run winetest under Linux, and because of that wrong environment setting, it got all the todo_wine's wrong. In fact, winetest.exe.so is built by default. Is that a mistake? - Dan
On Sun, Nov 07, 2004 at 03:48:53PM -0800, Dan Kegel wrote:
Ah, but you don't disable it, as far as I can tell. As of last month, I was able to run winetest under Linux, and because of that wrong environment setting, it got all the todo_wine's wrong. In fact, winetest.exe.so is built by default. Is that a mistake?
No. We still build winetest under Linux, so that it doesn't bitrot, but AFAIK, we reject submitted test results from such builds on WineHQ.
Dimitrie O. Paun wrote:
On Sun, Nov 07, 2004 at 03:48:53PM -0800, Dan Kegel wrote:
Ah, but you don't disable it, as far as I can tell. As of last month, I was able to run winetest under Linux, and because of that wrong environment setting, it got all the todo_wine's wrong. In fact, winetest.exe.so is built by default. Is that a mistake?
No. We still build winetest under Linux, so that it doesn't bitrot, but AFAIK, we reject submitted test results from such builds on WineHQ.
You may protect winehq from those reports, but there's still a problem: the local user (e.g. me :-) can get confused by the output of winetest on wine.
It's a minor thing, and the test results page for winehq that documents all this stuff will help, but I still have the feeling that winetest should disable the upload button and display a warning when running on Wine. And once that's been done, there's no harm in setting the environment variable correctly so winetest actually handles the todo_wine annotations correctly. - Dan
On Sun, 7 Nov 2004, Dimitrie O. Paun wrote: [...]
- winetest.exe currently assumes you're running under Windows.
See main.c line 577: (putenv ("WINETEST_PLATFORM=windows") || Wouldn't it be useful to allow Linux results to be computed and reported via winetest, too? Presumably it could detect that it's running on Linux somehow. (perhaps by running uname -a...)
It would be cool (and we support it), but in practical terms, it will be more of a problem (that's why we explicitely disable it). We know that all tests run under Wine/Linux anyway, so it would provide little additional benefit,
[...]
That's certainly not true of the sound tests. Those will fail on some machines depending on whether you use wineoss or winealsa or winearts, etc, and edpending on your soundcard. Some graphics tests may also be sensitive to the X bit depth or other environmental issues.
It's still possible to run the Linux tests via 'make test' and that may make winetest redundant on Linux to some extent. But we cannot claim that the 'tests run under Wine/Linux anyway'.
-
Dan Kegel -
Dimitrie O. Paun -
Francois Gouget