[autotest] email error about inconsistent host history
When host lock/unlock event was not recorded by metaDB, host history will
have some inconsistent value. The fix is to make history building smarter.
That is, if a dut has status changed while its lock status is True, assume
the dut is unlocked.
Before that fix is implemented, I'd like to add some report of this issue
to see how often that happens. If this becomes a serious issue, we might
want to force lock/unlock event being reported using http, instead of udp.
BUG=None
TEST=local run
/usr/local/autotest/site_utils/collect_host_stats.py --span 1 -e dshi@google.com
Change-Id: I295341682f96691af39a0cb1c3e97be2d2ded1ed
Reviewed-on: https://chromium-review.googlesource.com/226131
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
1 file changed
