Make sure pinpoint pass --gtest-benchmark-name flag whenever user trigger a C++ perf benchmark |
||
Issue descriptionThis is to ensure that benchmark name always match the test step name. Right now, it uses the benchmark binary name as the benchmark name when analyzing perf data. This doesn't work when we have different "benchmark run" on the same benchmark binary but with different flags (See issue 870692 for example). This should be done slowly to avoid breaking pinpoint.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
||
►
Sign in to add a comment |
||
Comment 1 by crouleau@chromium.org
, Jan 8