Folks,
As of today, winetest requires an email address to submit results to test.winehq.org. This is because it's often necessary to contact the submitter of a test to get more details, or to ask them to fix their setup, and it's often hard to guess the identity of the submitter from the tag name.
If you are morally offended at the idea of your email showing up in the result log, you can use some obfuscated format, or use your real name or IRC nick if you are well-known around these parts. The important thing is that Wine developers must be able to get in touch with you easily.
If you have some automated scripts submitting results, you'll need to fix them to pass a -m option to winetest.
On Mon, Feb 8, 2010 at 2:24 PM, Alexandre Julliard julliard@winehq.org wrote:
Folks,
As of today, winetest requires an email address to submit results to test.winehq.org. This is because it's often necessary to contact the submitter of a test to get more details, or to ask them to fix their setup, and it's often hard to guess the identity of the submitter from the tag name.
If you are morally offended at the idea of your email showing up in the result log, you can use some obfuscated format, or use your real name or IRC nick if you are well-known around these parts. The important thing is that Wine developers must be able to get in touch with you easily.
If you have some automated scripts submitting results, you'll need to fix them to pass a -m option to winetest.
FWIW, I've updated the build script on winezeug (http://winezeug.googlecode.com/svn/trunk/build_script/daily.sh) to handle it (by setting it yourself, or it will retrieve it from git, and as a last resort use $USER@$HOSTNAME).
I'm sure many of you have your own scripts, but I noticed at least a couple people are using my script on test.winehq.org...
-
Alexandre Julliard -
Austin English