mirror of
https://github.com/mvt-project/mvt.git
synced 2026-02-12 16:42:45 +00:00
Load Android device timezone info and add additional file modification logs (#567)
* Use local timestamp for Files module timeline. Most other Android timestamps appear to be local time. The results timeline is more useful if all the timestamps are consistent. I would prefer to use UTC, but that would mean converting all the other timestamps to UTC as well. We probably do not have sufficient information to do that accurately, especially if the device is moving between timezones.. * Add file timestamp modules to add logs into timeline * Handle case were we cannot load device timezone * Fix crash if prop file does not exist * Move _get_file_modification_time to BugReportModule * Add backport for timezone and fix Tombstone module to use local time. * Fix import for backported Zoneinfo * Fix ruff error
This commit is contained in:
committed by
GitHub
parent
e5865b166e
commit
4e97e85350
@@ -60,6 +60,8 @@ class TestTombstoneCrashArtifact:
|
||||
assert tombstone_result.get("pid") == 25541
|
||||
assert tombstone_result.get("process_name") == "mtk.ape.decoder"
|
||||
|
||||
# Check if the timestamp is correctly parsed, and converted to UTC
|
||||
# Original is in +0200: 2023-04-12 12:32:40.518290770+0200, result should be 2023-04-12 10:32:40.000000+0000
|
||||
assert tombstone_result.get("timestamp") == "2023-04-12 10:32:40.000000"
|
||||
# With Android logs we want to keep timestamps as device local time for consistency.
|
||||
# We often don't know the time offset for a log entry and so can't convert everything to UTC.
|
||||
# MVT should output the local time only:
|
||||
# So original 2023-04-12 12:32:40.518290770+0200 -> 2023-04-12 12:32:40.000000
|
||||
assert tombstone_result.get("timestamp") == "2023-04-12 12:32:40.000000"
|
||||
|
||||
Reference in New Issue
Block a user