Matt Riedemann 57aab15c11 Retry change queries on a 502 response ...

When gerrit is running slow we get 502 responses
back which kills the graph builder. We can retry
these requests from the client to keep going. Generally
a single retry fixes it.

Change-Id: I745d7c9b80ab8861972193d82c037df76af69e06

2017-10-09 20:18:58 -04:00

..

cmd

Retry change queries on a 502 response

2017-10-09 20:18:58 -04:00

tests

Retry change queries on a 502 response

2017-10-09 20:18:58 -04:00

__init__.py

Further shuffling to get this to fit the standard code layout

2013-09-25 18:20:51 -07:00

bot.py

Make Elastic Recheck Watch more reusable

2016-09-20 18:11:30 -07:00

config.py

Switch to jobs_re for config setting

2017-08-07 13:53:53 -04:00

elasticRecheck.py

Merge "Pass config from Stream to FailEvent"

2017-08-01 19:03:39 +00:00

loader.py

Add allow-nonvoting key

2016-02-01 07:55:30 -08:00

log.py

Make Elastic Recheck Watch more reusable

2016-09-20 18:11:30 -07:00

query_builder.py

Add zuul launcher completion message to result ready query

2016-06-29 18:31:08 -04:00

results.py

Wait until the most recent index is available

2016-10-20 10:48:55 -07:00