From e5e2496a1c32d6974683aac231a9a0e5dca573cf Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Thu, 2 Jul 2015 13:49:51 -0700 Subject: [PATCH] Point out that non-voting jobs are skipped in the readme From time to time we get a query change proposed that only hits on a non-voting job and we have to explain why we don't accept those, so add some wording to the readme about why non-voting jobs are skipped. Example: I6e4c031b1f3a8ea8ec910bc70510971972d052d3 Change-Id: I9c3ce7cbfa6fe841c31f9f4b39ff75bea900b691 --- README.rst | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index 8f148e01..96411a53 100644 --- a/README.rst +++ b/README.rst @@ -86,8 +86,12 @@ stack that can cause many tempest tests to fail. `_ and try to find a log that is associated with the failure. The closer to the root cause the better. - Note that queries can only be written against INFO level and higher log - messages. This is by design to not overwhelm the search cluster. + - Note that queries can only be written against INFO level and higher log + messages. This is by design to not overwhelm the search cluster. + - Since non-voting jobs are not allowed in the gate queue and e-r is + primarily used for tracking bugs in the gate queue, it doesn't spend time + tracking race failures in non-voting jobs since they are considered + unstable by definition (since they don't vote). #. Go to `logstash.openstack.org `_ and create an elastic search query to find the log message from step 1. To see the @@ -117,7 +121,7 @@ an aggregation of all failed gate jobs that don't currently have elastic-recheck fingerprints. Future Work ------------- +----------- - Move config files into a separate directory - Make unit tests robust