aboutsummaryrefslogtreecommitdiffhomepage
path: root/tools/nanobench_flags.py
Commit message (Collapse)AuthorAge
* Only use 256x256 tiles on hd2000 nanobench botsGravatar egdaniel2015-03-20
| | | | | | | | | | | Initial experiments did show that the 256 tile size fixed the hd2000 win7 nanobot failures. However it did not have any effect on other bots, so this change is to move back to the larger tile size on all bots expect for the hd2000. BUG=skia: Review URL: https://codereview.chromium.org/1022083002
* Fix bug in Valgrind flags config.Gravatar mtklein2015-03-10
| | | | | | | | | | | 'GPU' is in 'Test-Ubuntu14-GCE-NoGPU-x86_64-Release-Valgrind_CPU' too. This means we're building it in no-GPU mode, and running it in no-CPU mode. At least it finishes quite quickly this way (~10 seconds). BUG=skia: Review URL: https://codereview.chromium.org/992203004
* Run Valgrind bots with --nogpu and --nocpu as appropriateGravatar borenet2015-03-09
| | | | | | | BUG=skia:3506 NOPRESUBMIT=true Review URL: https://codereview.chromium.org/986583004
* Add msaa runs to nanobenchGravatar bsalomon2015-02-28
| | | | | | TBR=mtklein@google.com Review URL: https://codereview.chromium.org/964053002
* Add tools/nanobench_flags.py.Gravatar mtklein2015-02-24
This should look suspiciously similar to tools/dm_flags.py. In fact, I tweaked tools/dm_flags.py a bit to make it even more suspiciously similar. I'll leave actually deduping this to future me. I noticed we have an opportunity to make our Valgrind run of nanobench faster, by not only making it not auto-calibrate (--loops 1) but also take only one measurement (--samples 1). Should be 5-10x faster than the default. BUG=skia: Review URL: https://codereview.chromium.org/957503002