New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 699680 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Jun 2018
Cc:
█ dshi@chromium.org
akes...@chromium.org
davidri...@chromium.org
█ jrbarnette@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

TKO results are being added with a start time of None

Project Member Reported by davidri...@chromium.org, Mar 8 2017 
The AFE suite 105329911 corresponding to build snappy-release release-R58-9334.B:2 (id 1369123) has TKO entries with a finished time but a start time of None as returned by tko.get_job_test_statuses_from_db().

The relevant entry, which includes a finished time, is:
ERROR:root:TKO entry missing time: ['Exception waiting for results', '', 'bvt-inline'] bvt-inline FAIL Exception waiting for results None 2017-03-08 01:36:42 chromeos-test  105329911-chromeos-test/hostless 

It looks like the code that generate that event is autotest/files/server/cros/dynamic_suite/suite.py0

This is currently breaking the suite report, but I can work around it by ignoring start times of 'None'.  (Not sure why it's returning 'None' instead of None).
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 11 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/4fdcda985d8b56f391dfd1c98ac98ee83ec59416

commit 4fdcda985d8b56f391dfd1c98ac98ee83ec59416
Author: David Riley <davidriley@chromium.org>
Date: Sat Mar 11 08:35:21 2017

autotest: Make suite report handle missing TKO start times.

BUG= chromium:699680 
TEST=dump_suite_report 105329911

Change-Id: I4d352479823445b988b5e24dd3a9780b095a0d77
Reviewed-on: https://chromium-review.googlesource.com/451690
Commit-Ready: David Riley <davidriley@chromium.org>
Tested-by: David Riley <davidriley@chromium.org>
Reviewed-by: David Riley <davidriley@chromium.org>

[modify] https://crrev.com/4fdcda985d8b56f391dfd1c98ac98ee83ec59416/server/lib/suite_report.py

Comment 2 by autumn@chromium.org, Mar 21 2017

Owner: davidri...@chromium.org
Fixed I assume?

Comment 3 by davidri...@chromium.org, Mar 21 2017

Cc: davidri...@chromium.org
Owner: ----
No, I just did a work around.  

I'm not sure if I"m a good owner, I'm not at all familiar with that code and would much rather find someone who knows it and who can make a quick fix.

Comment 4 by aut...@google.com, Apr 4 2017

Labels: Hotlist-Fixit

Comment 5 by akes...@chromium.org, Sep 30 2017

Cc: dshi@chromium.org
Is this another instance?

https://luci-milo.appspot.com/buildbot/chromeos/whirlwind-paladin/9419
The suite report is really strange, and the suite ended up timing out, which makes me suspect it timed out due to suite_report choking on long timespan.
https://viceroy.corp.google.com/chromeos/suite_details?job_id=145819086

Comment 6 by davidri...@chromium.org, Sep 30 2017 

This sounds like https://bugs.chromium.org/p/chromium/issues/detail?id=735511

Also issue 761139

Comment 7 by cindyb@chromium.org, May 31 2018 

Hi, this bug has not been updated recently and remains untriaged. Please acknowledge the bug and provide status within two weeks (6/8/2018), or the bug will be closed. Thank you.

Comment 8 by cindyb@chromium.org, Jun 8 2018

Status: Archived (was: Untriaged)
Archiving per #7.
►

Sign in to add a comment