Fix and strengthen dual-GPU pixel tests.
Previously they were not checking whether they were running on the expected GPU (low-power or high-performance). In fact, they were accidentally misconfigured in test_suites.pyl, and were not exercising the desired code paths on the bots. Stop forcing the discrete GPU when running the pixel tests - allow them to use the natural GPU configuration of the browser - and make assertions about which GPU is active at various points during the low-to-high-power and high-to-low-power tests. Bug: 1047573 Change-Id: Icdb85c6fe2625ccce489f8bba4c053f5248e1e55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032190 Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by:James Darpinian <jdarpinian@chromium.org> Cr-Commit-Position: refs/heads/master@{#738051}
Showing
This diff is collapsed.
Please register or sign in to comment