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

Issue 614071 link

Starred by 4 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

test_droid event times in log are two hours ahead

Project Member Reported by bryanlew@chromium.org, May 23 2016

Issue description

test_droid will jump forward by two hours after the first log entry.  The first time is the actual/correct local time, the second and subsequent lines are +2 hours.  This +2 timestamp is applied to the line entries in all autoserv.* logs.

For example, here are the first few lines of test_droid execution/std[err,out]:

bryanlew@bryanlew0 files$ ./site_utils/test_droid.py whitelistedGtests
11:22:55 INFO | Began logging to /tmp/test_that_results_l_Zngh
Adding labels [u'cros-version:ad_hoc_build', u'board:ad_hoc_board'] to host localhost
13:22:55 INFO | Fetching suite for job named whitelistedGtests...
13:22:57 INFO | Scheduling suite for job named whitelistedGtests...
13:22:57 INFO | ... scheduled 1 job(s).

 
Status: Archived (was: Untriaged)
This bug has not been touched in over a year.  It is probably no longer relevant.

Sign in to add a comment