1370602 - Mismatch between android emulator timezone and host logging timezone

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: Testing, enhancement, P3)

Description

[Geoff Brown [:gbrown]]

There is a 7 hour difference (UTC vs Pacific probably) between android logcat timestamps and those in the main test log. It would be less confusing if they were consistent.

Comment 1

[Geoff Brown [:gbrown]]

The "host logging timezone" is really defined by run-task's datestamp:

https://dxr.mozilla.org/mozilla-central/rev/54063deb2f1caf8c4acf6461d3ba779805835c96/taskcluster/scripts/run-task#87

    now = datetime.datetime.utcnow().isoformat().encode('utf-8')

Comment 2

[Geoff Brown [:gbrown]]

I think the avd should probably use the host timezone by default, and android_emulator_unittest should explicitly set the timezone to utc with 'emulator -timezone ...'.

Comment 3

[Geoff Brown [:gbrown]]

...but -timezone Etc/UTC seems to have no effect.

Comment 4

[Geoff Brown [:gbrown]]

This is promising: adb logcat -v threadtime,UTC ...

Comment 5

[Geoff Brown [:gbrown]]

...but it doesn't work in the Android 4.3 environment!

Comment 6

[Firefox Bug Husbandry Bot]

Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.

Comment 7

[Geoff Brown [:gbrown]]

Today I checked Android 7.0 x86 logs vs in-log logcats vs logcat artifacts both before and after the recent daylight saving time change -- all times agreed. This issue is resolved for Android 7.0 x86.

Comment 8

[Geoff Brown [:gbrown]]

The mismatch remains for Android 4.3. I think the only way to address this is to update the timezone on the android images. I don't want to do that just for this issue; will keep this bug open as a reminder for the next time those images are modified.

Comment 9

[Geoff Brown [:gbrown]]

Android 4.3 is (practically) no longer a concern.