Non-essential tooling improvements
Add a new wrapper for executing the time zone tree visualization tool,
provide information about the wrapper in the README.android, and add some more
helpful logging the the tzlookup.xml generator.
Change how the tools are built / executed.
Add test_suite tags and test mappings to get the host tool tests running
automatically.
Test: Ran the tools
Test: atest tztools_common_tests telephonylookup_generator_tests tzlookup_tests
Change-Id: If1a19d2470bbec5d3132d66427e0cfd40ce60cc0
diff --git a/debug_tools/host/README.android b/debug_tools/host/README.android
index 7ea52ef..4926677 100644
--- a/debug_tools/host/README.android
+++ b/debug_tools/host/README.android
@@ -9,3 +9,17 @@
It also dumps human-readable CSV files of the (v1) content currently used by
Android's ZoneInfo class. These can be inspected and compared with dumps from
other tzdata files easily using your favourite text diffing tool.
+
+visualize_zone_trees.py
+ - A tool that visualizes time zones, specifically when time zones "sync up"
+ (i.e. stop being distinct). Time zone IDs are created in the tzdb whenever
+ there is a distinction between time zones, e.g. if a sub-region moved
+ from being the same as one major region to be the same as a different major
+ region, then a new time zone ID is required to represent the sub-region's
+ behavior because neither of the IDs for the major region describe the time
+ zone behavior of the sub-region throughout time. Once created, zone IDs
+ persist in the tzdb forever. Zone trees are used to determine if zone IDs
+ are still needed in order to represent relevant distinctions, e.g. does
+ Android still need to offer a choice between two zones that will be the
+ same from time X until the end of time? If the answer is no, one of the
+ zones can be used / shown to users and the other need not be.