DUT timestamps in kernel log vary between GMT and PST/PDT |
||||
Issue descriptionWe can deal with it, but it's one additional mental step when matching times of events across logs, and can easily confuse less experienced sheriffs. My guess is that the CMOS clock is kept in GMT all start in GMT, then figure out what time zone they are in, and adjust it. However, most of the kernel logs I see have a preponderance of GMT time stamps. Maybe there is a bias because I tend to look at logs for "device not pingable" or "DUT did not reboot" problems. Adding the time zone to the time stamps may be overkill. Maybe add a single character (like *) for GMT, and leave alone otherwise? Or maybe do nothing. :/
,
Feb 2 2017
What's actually being requested here? There's a known issue with /var/log/messages in Chrome OS shifting from GMT to the local timezone during boot. That's not a test infrastructure bug, it's a Chrome OS bug (and one we likely can't fix). I think it would be relatively easy to tinker with the timestamp in autotest logs to include a timezone, or to otherwise change the time format. Adding a timezone makes me nervous, though. That change would add quite a few columns to log files that get quite wide as is. I'm not sure that cost is worth the benefit.
,
Feb 2 2017
The question was whether to add a '*' to the time stamp when it's in GMT. We could also add 'GMT', but I agree that's a lot of columns. But I guess that the * won't really help with the confusion.
,
Feb 2 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by autumn@chromium.org
, Jan 24 2017