[next] telepathy-mission-control: document MC_TEST_KEEP_TEMP

[Simon McVittie]

Module: telepathy-mission-control
Branch: next
Commit: 04a2f757879caf21d474c03a5728ec5e1ffe7c29
URL:    http://cgit.freedesktop.org/telepathy/telepathy-mission-control/commit/?id=04a2f757879caf21d474c03a5728ec5e1ffe7c29

Author: Simon McVittie <simon.mcvittie at collabora.co.uk>
Date:   Wed Sep 18 19:42:56 2013 +0100

document MC_TEST_KEEP_TEMP

Bug: https://bugs.freedesktop.org/show_bug.cgi?id=69542
Reviewed-by: Guillaume Desmottes <guillaume.desmottes at collabora.co.uk>

---

 tests/twisted/README |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/tests/twisted/README b/tests/twisted/README
index ced06a2..b1b0716 100644
--- a/tests/twisted/README
+++ b/tests/twisted/README
@@ -16,7 +16,9 @@ To run with debug information:
 To debug an individual test you can set one of the following env variable:
 
   * MISSIONCONTROL_TEST_VALGRIND : to run Mission Control inside valgrind. The
-    report is added to missioncontrol.log.
+    report is added to missioncontrol.log. You'll probably also want
+    MC_TEST_KEEP_TEMP to keep the logs in tests/twisted/tmp-*, even when
+    tests passed.
 
   * MISSIONCONTROL_TEST_REFDBG : to run Mission Control inside refdbg. The
     report is written to refdbg.log. You can change