commit | ab6bdb66757f48fcaac8bc8953c5768a201d6bb3 | [log] [tgz] |
---|---|---|
author | Priyanka <priyankaspatel@google.com> | Mon May 13 15:41:48 2024 +0100 |
committer | Priyanka <priyankaspatel@google.com> | Tue May 14 10:25:36 2024 +0100 |
tree | 496ee489282715d1fcddc3bd50ea7ad61d494dc5 | |
parent | 8b89ea387cbb1b680dfcb69e7cafdc8186860bf5 [diff] |
Stop using persist.sys.time.offset Seems like it's not always accurate e.g. in bug below, sys.time.offset is 8 hours but sys.timezone gives offset of 7 hours for timestamps in trace. This means we have no need to include utcOffsetMs in the TimezoneInfo interface, as we're never going to be receiving it alongside the timezone string. Fixes: 340198224 Test: npm run test:unit:ci Change-Id: I020b2f4b189ae6e51bf1b636faec1161ffb13b91