Issue metadata
Sign in to add a comment
|
Set up an Android clang perf builder & tester |
||||||||||||||||||||||
Issue descriptionThe GCC-based toolchain provided by the NDK is decaying and is "no longer supported" as of r13b, the revision after chromium's current one. We are going to have to switch over to clang in the not-too-distant future. Before doing that, though, we ought to start collecting performance metrics on clang builds of chromium s.t. we can compare them to comparable gcc builds. This should include a full bot on chromium.perf, not just resource_sizes (though that should be part of it as well).
,
Dec 28 2016
FYI, labs are setting up an android bot in bug 667490 that is now somewhat redundant. If needed, that hardware could be used here.
,
Feb 13 2017
,
Feb 14 2017
,
Dec 4 2017
Moving Infra>Client>Android -> Infra>Client>Chrome+OS=Android
,
Dec 4 2017
,
Dec 4
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 4
Android is on clang by default nowadays. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jbudorick@chromium.org
, Dec 22 2016