| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
new trace events checked in by: http://trac.webkit.org/changeset/128785 to properly track WebGL and accelerated canvas instead of relying on
the swap-buffers calls (which get issued anyway, when in FCM).
This patch has most of the contents of: https://codereview.chromium.org/10914247 except that it doesn't change any of the field trial probabilities.
It fixes the following tests: Canvas2DDisabled, Canvas2DBlocked, WebGLBLocked, WebGLDisabled, AcceleratedCompositingDisabled,
AcceleratedCompositingBlocked .
It also disables ExtensionApiTest.CaptureVisibleTabJPeg as it triggers flakiness on it. chrome.tabs.captureVisibleTab is inherently racy as there is no way to guarantee that the tab has been painted at least once when that call is made. Note how the other variants of CaptureVisibleTab tests have already been disabled for similar reasons. (this was done with aa@'s advice)
BUG=155336
Review URL: https://chromiumcodereview.appspot.com/11091072
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161733 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=146448
TEST=None
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=160144
Review URL: https://codereview.chromium.org/11026015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160174 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=146448
TEST=None
Review URL: https://codereview.chromium.org/11026015
TBR=davemoore@chromium.org
Review URL: https://codereview.chromium.org/11030029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160145 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=146448
TEST=None
Review URL: https://codereview.chromium.org/11026015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160144 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. threaded compositing on windows (except XP)
2. force compositing mode on mac
On linux we switch to a 1/3 1/3 fcm and thread experiments .
This patch also gives priority to the command line switches so that both threaded
and force compositing mode can be turned off via the about:flags page or command line.
In the near future, we will use the Finch framework to tweak the experiment percentages.
Note: This patch has a dependency on:
https://bugs.webkit.org/show_bug.cgi?id=96871
It also disables ExtensionApiTest.CaptureVisibleTabJPeg as it triggers flakiness on it. chrome.tabs.captureVisibleTab is inherently racy as there is no way to guarantee that the tab has been painted at least once when that call is made. Note how the other variants of CaptureVisibleTab tests have already been disabled for similar reasons.
BUG=143809,128387,146861
Review URL: https://chromiumcodereview.appspot.com/10914247
Reverted due to failures on Mac bots:
http://build.chromium.org/p/chromium.mac/builders/Mac10.6%20Tests%20%281%29/builds/29446/steps/interactive_ui_tests/logs/AutoResize
http://build.chromium.org/p/chromium.mac/builders/Mac10.7%20Tests%20%281%29/builds/2143/steps/interactive_ui_tests/logs/TightAutosizeAroundSingleLine
http://build.chromium.org/p/chromium.mac/builders/Mac%2010.6%20Tests%20%28dbg%29%283%29/builds/26358/steps/interactive_ui_tests/logs/TightAutosizeAroundSingleLine
http://build.chromium.org/p/chromium.mac/builders/Mac%2010.7%20Tests%20%28dbg%29%283%29/builds/1804/steps/interactive_ui_tests/logs/TightAutosizeAroundSingleLine
TBR=vangelis@chromium.org
Review URL: https://codereview.chromium.org/10991032
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158711 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. threaded compositing on windows (except XP)
2. force compositing mode on mac
On linux we switch to a 1/3 1/3 fcm and thread experiments .
This patch also gives priority to the command line switches so that both threaded
and force compositing mode can be turned off via the about:flags page or command line.
In the near future, we will use the Finch framework to tweak the experiment percentages.
Note: This patch has a dependency on:
https://bugs.webkit.org/show_bug.cgi?id=96871
It also disables ExtensionApiTest.CaptureVisibleTabJPeg as it triggers flakiness on it. chrome.tabs.captureVisibleTab is inherently racy as there is no way to guarantee that the tab has been painted at least once when that call is made. Note how the other variants of CaptureVisibleTab tests have already been disabled for similar reasons.
BUG=143809,128387,146861
Review URL: https://chromiumcodereview.appspot.com/10914247
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158707 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds an experiment that we can set to enable Stage3D on XP (where not completely blacklisted). It will be disabled by default.
BUG=136447
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=157910
Review URL: https://chromiumcodereview.appspot.com/10944037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158078 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds an experiment that we can set to enable Stage3D on XP (where not completely blacklisted). It will be disabled by default.
BUG=136447
Review URL: https://chromiumcodereview.appspot.com/10944037
TBR=jbauman@chromium.org
Review URL: https://codereview.chromium.org/10969030
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157925 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds an experiment that we can set to enable Stage3D on XP (where not completely blacklisted). It will be disabled by default.
BUG=136447
Review URL: https://chromiumcodereview.appspot.com/10944037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157910 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This also fixes the bug that GPU histograms are missing.
BUG=151057
TEST=tree
R=jbauman
Review URL: https://codereview.chromium.org/10911315
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157851 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
compositing mode field trial. This is in preparation for switching to using Finch to drive the field trial percentages.
This is identical to https://chromiumcodereview.appspot.com/10911161/ which because of a file move got too messy to merge for a git novice like myself... :(
BUG=
Review URL: https://chromiumcodereview.appspot.com/10913186
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155942 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When it's on the content side, it can be part of the GpuDataManager, so we don't need to make it a Singleton.
Also, this CL did some cleanup related to this moving.
The main reason for this refactoring is because blacklist is tightly coupled with GpuDataManager. Putting them on the this side makes it much easier to test the code, and the design is much better.
BUG=
TEST=bots
Review URL: https://chromiumcodereview.appspot.com/10907106
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155823 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%282%29/builds/6902/steps/browser_tests/logs/stdio
FAILED (3): GpuFeatureTest.AcceleratedCompositingBlocked
FAILED (5): GpuFeatureTest.WebGLBlocked
FAILED (7): GpuFeatureTest.MultisamplingBlocked
FAILED (9): GpuFeatureTest.Canvas2DBlocked
chrome/test/gpu/gpu_feature_browsertest.cc:343: Failure
Value of: content::GPU_FEATURE_TYPE_ACCELERATED_2D_CANVAS
Actual: 1
Expected: type
Which is: 0
chrome/test/gpu/gpu_feature_browsertest.cc:133: Failure
Value of: size_t(0)
Actual: 0
Expected: analyzer_->FindEvents(Query::EventName() ==
Query::String("SwapBuffers"), &events)
Which is: 3
chrome/test/gpu/gpu_feature_browsertest.cc:290: Failure
Value of: content::GPU_FEATURE_TYPE_MULTISAMPLING
Actual: 8
Expected: type
Which is: 0
When it's on the content side, it can be part of the GpuDataManager, so we don't need to make it a Singleton.
Also, this CL did some cleanup related to this moving.
The main reason for this refactoring is because blacklist is tightly coupled with GpuDataManager. Putting them on the this side makes it much easier to test the code, and the design is much better.
BUG=
TEST=bots
Review URL: https://chromiumcodereview.appspot.com/10908110
TBR=zmo@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10907098
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155223 0039d316-1c4b-4281-b951-d872f2087c98
|
|
When it's on the content side, it can be part of the GpuDataManager, so we don't need to make it a Singleton.
Also, this CL did some cleanup related to this moving.
The main reason for this refactoring is because blacklist is tightly coupled with GpuDataManager. Putting them on the this side makes it much easier to test the code, and the design is much better.
BUG=
TEST=bots
Review URL: https://chromiumcodereview.appspot.com/10908110
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155218 0039d316-1c4b-4281-b951-d872f2087c98
|