Subscribe to Test Results: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Updated for clarity and a more extensive listing of files to inspect. |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
<<< | To add (or remove) your email to nightly test-results emails: | ||
* Check out and/or update <code>$G/common/build/site</code> and <code>$G/common/build/valid</code> from CVS. | |||
** In the <code>site</code> directory, look at the files <code>test.platform.cfg</code>, <code>test.platform_critical.cfg</code>, and <code>test.platform_slow.cfg</code>. | |||
** In the <code>valid</code> directory, look at the <code>test.platform_*.cfg</code> files, particularly <code>test.platform_vrl.cfg</code>. | |||
*** Note: I (jadrian) am not really sure whether the scripts in "valid" run, and if so, what they're for. Worth somebody investigating. | |||
* Read the instructions in the comment at the top of each file. | |||
* Add your name to the list of emails anywhere you would like to be notified. | |||
* Save the files you edit, and then commit them. | |||
=== Deprecated notes for the old version of $G === | |||
Tests are run daily and mail is sent when an individual tests fail. | Tests are run daily and mail is sent when an individual tests fail. | ||
A summary of each test run is sent as well. | A summary of each test run is sent as well. | ||
| Line 10: | Line 19: | ||
<testname> <testowners>,... <testarchs>,... <testcommand>;... | <testname> <testowners>,... <testarchs>,... <testcommand>;... | ||
<testname> a directory in $G/src/ | <testname> a directory in $G/src/ | ||
<testowners> subscribers for individual tests | <testowners> subscribers for individual tests | ||
<testarchs> | <testarchs> linux | WIN32 | OSX | sol | sgi | ||
<testcommand> Commands to run a test separated by a semicolon. | <testcommand> Commands to run a test separated by a semicolon. | ||
usually: $G/bin/gfxtest-project <projectname> | usually: $G/bin/gfxtest-project <projectname> | ||
| Line 26: | Line 35: | ||
EMAILS="you@cs.brown.edu,me@cs.brown.edu" | EMAILS="you@cs.brown.edu,me@cs.brown.edu" | ||
[[Category:$G HOWTO]][[Category:Software Development]] | |||
Latest revision as of 13:41, 24 September 2013
To add (or remove) your email to nightly test-results emails:
- Check out and/or update
$G/common/build/siteand$G/common/build/validfrom CVS.- In the
sitedirectory, look at the filestest.platform.cfg,test.platform_critical.cfg, andtest.platform_slow.cfg. - In the
validdirectory, look at thetest.platform_*.cfgfiles, particularlytest.platform_vrl.cfg.- Note: I (jadrian) am not really sure whether the scripts in "valid" run, and if so, what they're for. Worth somebody investigating.
- In the
- Read the instructions in the comment at the top of each file.
- Add your name to the list of emails anywhere you would like to be notified.
- Save the files you edit, and then commit them.
Deprecated notes for the old version of $G
Tests are run daily and mail is sent when an individual tests fail. A summary of each test run is sent as well.
- Subscribe to failure notifications for an individual test
- Checkout and carefully edit: src/gfxtest/gfxtest.cfg
- Each line specifies a test to be run and contains:
<testname> <testowners>,... <testarchs>,... <testcommand>;...
<testname> a directory in $G/src/
<testowners> subscribers for individual tests
<testarchs> linux | WIN32 | OSX | sol | sgi
<testcommand> Commands to run a test separated by a semicolon.
usually: $G/bin/gfxtest-project <projectname>
- Blank lines are permitted. There is no provision for comment lines.
- Subscribe to receive test summaries
- Checkout and carefully edit: src/gfxtest/gfxtest-nightly
- Modify the first command in the script to add the recipient's mail address.
EMAILS="you@cs.brown.edu,me@cs.brown.edu"