| commit | a90b243e46da21a64872626e1e9bcaa18d51e437 | [log] [tgz] |
|---|---|---|
| author | Vadim Tryshev <vadimt@google.com> | Thu Apr 05 13:50:38 2018 -0700 |
| committer | Vadim Tryshev <vadimt@google.com> | Fri Apr 06 12:25:40 2018 -0700 |
| tree | 41f889c8c0a00b11e8aaba64b30a5076d2264516 | |
| parent | 271ba383b6bfa07a97e4f5dd65a89679e0270bd7 [diff] |
Improving jank tests diagnostics When there were 0 total frames, ProfileData generates something like: Janky frames: 0 (nan%) Then the test fails to parse it, and ends up with a mysterious "Failed to parse NUM_JANKY" diag (see the bug). Making the case 0/0 a 0%. Bug: 77528721 Test: atest google/perf/jank/SystemUI/UbSystemUIJankTests:android.platform.systemui.tests.jank.LauncherJankTests#testOpenAllAppsContainer Change-Id: Ib65b80dc689f7b6ee06b108114ffd7de9d739721