PGO build profiling refers to non-existing indexeddb test |
||
Issue descriptionPGO builds fail to find storage.indexeddb_endure_tracing. Since there is no check that the test ran the only thing that happens is this error message: No benchmark named "storage.indexeddb_endure_tracing". Do you mean any of those benchmarks below? Available benchmarks are: multipage_skpicture_printer It disappeared (I think, if I understood mharanczyk correctly) at https://bugs.chromium.org/p/chromium/issues/detail?id=717539 Example build: https://build.chromium.org/p/chromium.fyi/builders/Chromium%20Win%20x64%20PGO%20Builder/builds/22060 (There is also a ton of tests that time out) We noticed this because we used that same test for Opera PGO builds but we don't believe it added much so we don't miss it.
,
Dec 11 2017
Lowering the priority of the PGO bugs as we've switched the official build to Clang. I'll close these bugs once we decide that we won't support the VS build anymore.
,
Feb 27 2018
WontFix'ing this issue as the switch to Clang make it obsolete. |
||
►
Sign in to add a comment |
||
Comment 1 by sebmarchand@chromium.org
, Oct 21 2017