From b38578664a97b4843ad54fd91573bf77b605c0b4 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Wed, 19 Jun 2013 15:09:56 -0400 Subject: [PATCH] fix h1 formatting bug, add better overview Change-Id: Ib9234fcd58242e0e7b5f6c43c4ee06848ab521e1 Reviewed-on: https://review.openstack.org/33688 Approved: Jeremy Stanley Reviewed-by: Jeremy Stanley Tested-by: Jenkins --- .../files/logs/help/tempest-overview.html | 21 +++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/modules/openstack_project/files/logs/help/tempest-overview.html b/modules/openstack_project/files/logs/help/tempest-overview.html index c783be3120..edc7c343b9 100644 --- a/modules/openstack_project/files/logs/help/tempest-overview.html +++ b/modules/openstack_project/files/logs/help/tempest-overview.html @@ -1,9 +1,19 @@ -

Guide to Tempest Results Runs

+

Guide to Tempest Results Runs

-The directory here contains the full results of a devstack setup and -tempest run for the OpenStack gate, as well as all the logs of all the -relevant services that were running during that tempest test run. From -them you should have enough information to debug. + You are looking at the full test results of a devstack setup and + tempest run for the OpenStack gate, as well as all the logs of all the + relevant services that were running during that tempest test run. From + them you should have enough information to debug. +

+

How To Debug - Quickstart

+

+

    +
  1. scroll to the end of console.html +
  2. work your way backwards until the first failing test +
  3. copy the timestamp of that failing test +
  4. go into logs directory and look at that time stamp in related + service logs for traces, failures, or other oddities +

File Overview

console.html

@@ -33,7 +43,6 @@ job. The basic flow of the file goes as follows: The logs directory contains all the screen logs from all the services during the devstack-gate run.

-

About this Help

This help file is part of the openstack-infra/config project, and