Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(17)

Issues Search
    My Issues | Starred     Open | Closed | All

Unified Diff: chrome/test/perf/frame_rate/frame_rate_tests.cc

Issue 8386007: Used use-gl=any instead of forcing osmesa for UI tests. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/
Patch Set: Created 9 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « chrome/test/gpu/webgl_conformance_tests.cc ('k') | chrome/test/ui/ui_test.h » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/test/perf/frame_rate/frame_rate_tests.cc
===================================================================
--- chrome/test/perf/frame_rate/frame_rate_tests.cc (revision 107998)
+++ chrome/test/perf/frame_rate/frame_rate_tests.cc (working copy)
@@ -47,10 +47,6 @@
FrameRateTest() {
show_window_ = true;
dom_automation_enabled_ = true;
- // Since this is a performance test, try to use the host machine's GPU
- // instead of falling back to software-rendering.
- force_use_osmesa_ = false;
- disable_accelerated_compositing_ = false;
}
virtual FilePath GetDataPath(const std::string& name) {
« no previous file with comments | « chrome/test/gpu/webgl_conformance_tests.cc ('k') | chrome/test/ui/ui_test.h » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698