We do not currently always explicitly set the name of stories in story sets. It then defaults to using the URL (which sometimes gets transformed to be compatible with the perf dashboard).
We want to add explicit names to these stories so that we can easily reason about what name to use when disabling tests, sending test data to the dashboard, sending test data to the flakiness dashboard, and reading the output of the test in the logs.
Doing this will require migration of data on the perf dashboard so we do not lose historical data when we switch names.
Simon/Annie can you give us some information on the cost of doing these data migrations? We would ideally only limit this naming to benchmarks/story sets we know for sure we will not be turning down in the near future. A good example of this would be the loading.mobile benchmark.
Comment 1 by sullivan@chromium.org
, May 9 2017