summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/automated_builds_and_tests
diff options
context:
space:
mode:
authorbertagaz <bertagaz@ptitcanardnoir.org>2015-10-13 13:28:22 +0200
committerbertagaz <bertagaz@ptitcanardnoir.org>2015-10-13 13:31:58 +0200
commit80c04a126a10e8a3b6726d9008aeb3bec44198e7 (patch)
tree29b7332cbf29c93c8e4904c8b4bf48f032d4b472 /wiki/src/blueprint/automated_builds_and_tests
parente0efa41a15eaacdac0044366993d042a62f6ed01 (diff)
Update blueprint.
Diffstat (limited to 'wiki/src/blueprint/automated_builds_and_tests')
-rw-r--r--wiki/src/blueprint/automated_builds_and_tests/jenkins.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/wiki/src/blueprint/automated_builds_and_tests/jenkins.mdwn b/wiki/src/blueprint/automated_builds_and_tests/jenkins.mdwn
index b78335d..3fca162 100644
--- a/wiki/src/blueprint/automated_builds_and_tests/jenkins.mdwn
+++ b/wiki/src/blueprint/automated_builds_and_tests/jenkins.mdwn
@@ -9,7 +9,7 @@ Restarting slave VMs between jobs
This question is tracked in [[!tails_ticket 9486]].
-When we tackle [[!tails_ticket 5288]], if the test suite doesn't
+For [[!tails_ticket 5288]] to be robust enough, if the test suite doesn't
_always_ clean between itself properly (e.g. when tests simply hang
and timeout), we might want to restart `isotesterN.lizard` between
each each ISO testing job.