-
Caleb Rouleau authored
Remove "options = {'story_tag_filter_exclude': 'is_4k,is_50fps'}" This isn't really a good way to do this because of the following. if you run the code like this: $ ./tools/perf/run_benchmark run media.mobile --browser=android-chrome then the filter will work: number of stories 22 but if you run the code like this then $ ./tools/perf/run_benchmark run media.mobile --browser=android-chrome --story-tag-filter-exclude='other_tag' then the filter will not work: number of stories 29 (which means the 4k stories and 50fps stories were not excluded.) This is because the "options" simply sets the default "--story-tag-filter-exclude" So when a user provides a different value, the default is overriden. My change fixes this such that you can use that flag without side effects. It also helps by making the other parts of the system be able to know by default what stories are in the page_set. You can see that this is true because the the autogenerated benchmark.csv file now has fewer tags for media.mobile because of the filtered stories. I am attempting to redesign this system a bit for https://goo.gl/JZ2yZQ. I noticed this code. Also remove tag = 'android' since it doesn't do anything. Bug: 894254 Change-Id: Ibf5f90e83062c785934af334c8dd6bfde89cef25 Reviewed-on: https://chromium-review.googlesource.com/c/1356320 Commit-Queue: Caleb Rouleau <crouleau@chromium.org> Reviewed-by:Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#612840}
5f53d960