diff options
author | Robert Collins <robertc@robertcollins.net> | 2012-12-06 18:12:30 +1300 |
---|---|---|
committer | Robert Collins <robertc@robertcollins.net> | 2012-12-06 18:12:30 +1300 |
commit | 0b2787c76e14cef0fbc1ec380897396f14ac5771 (patch) | |
tree | f4e0686f73ba91748750ca41aa8ec9f450100107 /doc | |
parent | 1aa73ebfa32b9a3e0001f967d7d4e49d7cc01803 (diff) | |
download | testrepository-0b2787c76e14cef0fbc1ec380897396f14ac5771.tar.gz |
* ``testr last`` now supports ``--subunit`` and when passed will output
the stored subunit stream. Note that the exit code is always 0 when this
is done (unless an exception occurs reading the stream) - subunit consumers
should parse the subunit to determine success/failure. (Robert Collins)
Diffstat (limited to 'doc')
-rw-r--r-- | doc/MANUAL.txt | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/doc/MANUAL.txt b/doc/MANUAL.txt index d1e31bb..a0f0bcb 100644 --- a/doc/MANUAL.txt +++ b/doc/MANUAL.txt @@ -155,14 +155,6 @@ the worker that executed the test. The tags are of the form ``worker-%d`` and are usually used to reproduce test isolation failures, where knowing exactly what test ran on a given backend is important. -To find the tests that ran on a single slave:: - - $ testr last - # grab the id from that. - $ subunit-filter -s --xfail --with-tag=worker-3 < .testrepository/$lastid | subunit-ls > slave-3.list - -This will be better integrated in future. - To find out which slave a failing test ran on just look at the 'tags' line in its test error:: @@ -172,6 +164,10 @@ its test error:: ---------------------------------------------------------------------- error text +And then find tests with that tag:: + + $ testr last --subunit | subunit-filter -s --xfail --with-tag=worker-3 | subunit-ls > slave-3.list + Hiding tests ~~~~~~~~~~~~ |