Get better logging to explain TKO update failures
Reported by
jrbarnette@chromium.org,
Jun 27 2017
|
|||||||
Issue description
From time-to-time, we see tests fail because the TKO doesn't
get updated, as described in bug 589673.
Nominally, there are three theories for why that bug might be
happening:
1) Parsing makes updates in the TKO, and CloudSQL silently
drops them without signaling an error.
2) Parsing is somehow ignoring errors during updates.
3) Parsing is failing to make the updates at all.
We need to add log messages to parsing sufficient to distinguish
the three cases, so that we can make progress on addressing the
core bug.
,
Jun 29 2017
that, or metrics on tko failures.
,
Jun 29 2017
,
Jun 29 2017
At a higher level, the ask here is "whatever it takes to add information that will move bug 589673 further down the field."
,
Jul 10 2017
dshi to add read-back of tko inside of tko/parse to rule out mysql silently dropping transactions
,
Jul 10 2017
note for follow-up: after ^ we should ensure that scheduler determine's tko/parse return code and treats non-zero return codes appropriately
,
Jul 10 2017
,
Jul 17 2017
CL coming this week.
,
Jul 19 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/b0af621a3eda3d41b49db01f0f38f557fab9956a commit b0af621a3eda3d41b49db01f0f38f557fab9956a Author: Dan Shi <dshi@google.com> Date: Wed Jul 19 08:23:39 2017 [autotest] Read tko tests from database after it's saved. This is to confirm the CloudSQL instance has tko data saved. BUG= chromium:737157 TEST=local run tests Change-Id: Ibe3547363f2bd2ae9d590c95949e3f296827bdca Reviewed-on: https://chromium-review.googlesource.com/575436 Commit-Ready: Dan Shi <dshi@google.com> Tested-by: Dan Shi <dshi@google.com> Reviewed-by: Aviv Keshet <akeshet@chromium.org> [modify] https://crrev.com/b0af621a3eda3d41b49db01f0f38f557fab9956a/tko/db.py [modify] https://crrev.com/b0af621a3eda3d41b49db01f0f38f557fab9956a/tko/parse.py
,
Jul 24 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jrbarnette@chromium.org
, Jun 27 2017