Closed Bug 1370602 Opened 7 years ago Closed 4 years ago

Mismatch between android emulator timezone and host logging timezone

Categories

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

enhancement

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: gbrown, Unassigned)

References

Details

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.
Priority: -- → P2
Blocks: 1425322
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')
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 ...'.
...but -timezone Etc/UTC seems to have no effect.
This is promising: adb logcat -v threadtime,UTC ...
...but it doesn't work in the Android 4.3 environment!
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.
Priority: P2 → P5
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.
Priority: P5 → P3
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.
Assignee: gbrown → nobody

Android 4.3 is (practically) no longer a concern.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.