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

Issue 694862 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ shyamsundarp@google.com
█ jrbarnette@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

test_that timezone inconsistent in/out of board sysroot | test_that autotest reporting in central time locally

Project Member Reported by sbasi@chromium.org, Feb 22 2017 
$ test_that chromeos4-row1-rack10-host11.cros dummy_Pa
ssServer --autotest_dir ../third_party/autotest/files/

17:27:18 INFO | Began logging to /tmp/test_that_results_EzXo_8
Adding labels [u'cros-version:ad_hoc_build', u'board:leon'] to host chromeos4-row1-rack10-host11.cros
19:27:19 INFO | Fetching suite for job named dummy_PassServer...
19:27:23 INFO | Scheduling suite for job named dummy_PassServer...
19:27:23 INFO | ... scheduled 1 job(s).

Very odd.

Comment 1 by akes...@chromium.org, Feb 22 2017 

When you first run test_that, it runs from the source tree  checkout in your chroot. However, once it figures out what board you're using, it jumps into the board sysroot and re-executes itself.

Probably there's a timezone behavior difference between the default python in the chroot, and the board-sysroot python.

Comment 2 by xixuan@chromium.org, Feb 22 2017 

In our default django path: site-packages/django/conf/global_settings.py, TIME_ZONE is set as 'America/Chicago'.

We can change it to 'America/Los_Angeles' or 'Etc/GMT+8'.

Comment 3 by akes...@chromium.org, Mar 8 2017

Labels: Hotlist-Fixit
Owner: ----
Status: Available (was: Untriaged)
Summary: test_that timezone inconsistent in/out of board sysroot | test_that autotest reporting in central time locally (was: test_that autotest reporting in central time locally)
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 9 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment