| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
sync.SyncIntegrationTest
R=dyu@chromium.org
BUG=
TEST=
Review URL: http://codereview.chromium.org/8510073
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110005 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a WebUIBrowserTest for WebUI Hung Renderer Dialog.
Also modifies HungRendererDialog to allow it to be called in a test without killing processes or restarting hang timers.
See previous attempt: http://codereview.chromium.org/8372042
See revert of that attempt: http://codereview.chromium.org/8497001/
BUG=102073
TEST=browser_tests HungRendererDialogUITest.*
Review URL: http://codereview.chromium.org/8462015
TBR=wyck@chromium.org
Review URL: http://codereview.chromium.org/8510071
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109989 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=104179
TEST=none
Review URL: http://codereview.chromium.org/8564031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109988 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a WebUIBrowserTest for WebUI Hung Renderer Dialog.
Also modifies HungRendererDialog to allow it to be called in a test without killing processes or restarting hang timers.
See previous attempt: http://codereview.chromium.org/8372042
See revert of that attempt: http://codereview.chromium.org/8497001/
BUG=102073
TEST=browser_tests HungRendererDialogUITest.*
Review URL: http://codereview.chromium.org/8462015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109984 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
sync.SyncIntegrationTest.testAddBookmarkAndVerifySync in Win platforms
notifications.NotificationsTest.testKillNotificationProcess in Linux
BUG=104179, 104206
Review URL: http://codereview.chromium.org/8566017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109970 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
subdirectories.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8491036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109951 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/8565020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109945 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8552004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109917 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8508044
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109909 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
It has been timing out about 5-10% of the time on Linux bots.
TBR=zmo@chromium.org
BUG=104142
Review URL: http://codereview.chromium.org/8510059
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109893 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=104039
R=ben@chromium.org
Review URL: http://codereview.chromium.org/8497067
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109887 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[Nope, definitely flaky. Timed out on Linux.]
The bug is uninformative and I don't see how this out-of-process test can be any
flakier than the other out-of-process tests (for the example failure in the
bug). So let's try reenabling it.
BUG=91729
TBR=dmichael@chromium.org
Review URL: http://codereview.chromium.org/8530004
TBR=viettrungluu@chromium.org,dmichael@chromium.org
Review URL: http://codereview.chromium.org/8548004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109824 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bug is uninformative and I don't see how this out-of-process test can be any
flakier than the other out-of-process tests (for the example failure in the
bug). So let's try reenabling it.
BUG=91729
TBR=dmichael@chromium.org
Review URL: http://codereview.chromium.org/8530004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109822 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This only enables extension functions. I will do events in a
separate change.
BUG=81760,80308
Review URL: http://codereview.chromium.org/8540012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109812 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
To be landed after http://codereview.chromium.org/8537026/.
BUG=103955,103969
TBR=yzshen@chromium.org,dmichael@chromium.org
Review URL: http://codereview.chromium.org/8540029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109788 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Removing dependencies from content/.
BUG=102224
Review URL: http://codereview.chromium.org/8498034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109749 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
(Retry after a fix.)
The general idea is to use jbates's newly added tracing: if a feature is blacklisted, we check the tracing data to make sure gpu process hasn't launched.
BUG=101222
TEST=browser_tests
Review URL: http://codereview.chromium.org/8510032
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109740 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
chrome on Vista uses accelerated canvas even without accelerated compositing. So to force software, we need --disable-accelerated-2d-canvas.
Additionally, to avoid potential flakiness, moved the check from context creation success to actual swap buffers - that way if someone creates a context without drawing, it will not trigger.
BUG=103956
Review URL: http://codereview.chromium.org/8491056
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109727 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=PPAPITest.FlashClipboard passes.
Review URL: http://codereview.chromium.org/8515014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109724 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I believe these tests were originally flaky due to unclean state on the
bots running the tests. The bots have been cleaned of the problem. I ran
these tests on the Win7 QA bot, and also the Mac 10_6 QA bot, and all of the
tests passed with --repeat=100.
BUG=85598
TEST=None
Review URL: http://codereview.chromium.org/8538022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109722 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
http://chromegw.corp.google.com/i/chromium/builders/Vista%20Tests%20%282%29/builds/11639
BUG=103955
TBR=viettrungluu@chromium.org
Review URL: http://codereview.chromium.org/8540020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109713 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Add test for Bug 99970 Comment 6 & fix
2) Allow chrome.send to be mocked outside of preLoad call.
3) add chrome.originalSend to allow mocked messages to pass through to C++.
Also to address need for .cc file to be correct for clang, and prevent ugliness in js with a lot of GEN lines, allow the header and .cc to not have a suffix, and the generated file to end in -gen.cc. While doing this, addressed crbug.com/102794 to put in <(INTERMEDIATE_DIR) preventing collisions across rules.
R=flackr@chromium.org,wyck@chromium.org
BUG=103740,99970,102794
TEST=browser_tests --gtest_filter=Mock4JS*.* AND ChromeSend*.*
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=109678
Review URL: http://codereview.chromium.org/8515016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109711 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/8527017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109691 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:19759
TEST=run_remote_tests.sh --board=x86-generic desktopui_PyAutoFunctionalTests.control.vm
Change-Id: Ibc7caa932991cc902a4aa50c2974bb4bc87f2eea
Review URL: http://codereview.chromium.org/8526026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109684 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
chrome.send passthrough.
1) Add test for Bug 99970 Comment 6 & fix
2) Allow chrome.send to be mocked outside of preLoad call.
3) add chrome.originalSend to allow mocked messages to pass through to C++.
Also to address need for .cc file to be correct for clang, and prevent ugliness in js with a lot of GEN lines, allow the header and .cc to not have a suffix, and the generated file to end in -gen.cc. While doing this, addressed crbug.com/102794 to put in <(INTERMEDIATE_DIR) preventing collisions across rules.
R=flackr@chromium.org,wyck@chromium.org
BUG=103740,99970,102794
TEST=browser_tests --gtest_filter=Mock4JS*.* AND ChromeSend*.*
Review URL: http://codereview.chromium.org/8515016
TBR=scr@chromium.org
Review URL: http://codereview.chromium.org/8480027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109680 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
disabled code for OpenBSD:
- AdjustRendererOOMScore()
- SECCOMP_SANDBOX
BUG=
TEST=compile
Review URL: http://codereview.chromium.org/8341052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109679 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Add test for Bug 99970 Comment 6 & fix
2) Allow chrome.send to be mocked outside of preLoad call.
3) add chrome.originalSend to allow mocked messages to pass through to C++.
Also to address need for .cc file to be correct for clang, and prevent ugliness in js with a lot of GEN lines, allow the header and .cc to not have a suffix, and the generated file to end in -gen.cc. While doing this, addressed crbug.com/102794 to put in <(INTERMEDIATE_DIR) preventing collisions across rules.
R=flackr@chromium.org,wyck@chromium.org
BUG=103740,99970,102794
TEST=browser_tests --gtest_filter=Mock4JS*.* AND ChromeSend*.*
Review URL: http://codereview.chromium.org/8515016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109678 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test was failing in the debug build of Chromium when I was
enabling NaCl tests on Mac OS X the other month. It now seems to be
passing, so let's enable it.
BUG=http://code.google.com/p/nativeclient/issues/detail?id=2077
TEST=nacl_integration
Review URL: http://codereview.chromium.org/8506002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109582 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Try bots cannot handle patches with binary files nicely.
We should add this file before adding a test that depends
on the file.
% unzip -l chrome/test/data/zip/evil_via_absolute_file_name.zip
Archive: chrome/test/data/zip/evil_via_absolute_file_name.zip
Length Date Time Name
--------- ---------- ----- ----
4 2011-11-09 23:40 /evil.txt
--------- -------
4 1 file
BUG=chromium-os:22351
TEST=none
Review URL: http://codereview.chromium.org/8523015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109536 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Diable run_ppapi_ppp_input_event_browser_test nacl_integration test.
Fails only on Windows. Nacl folk are looking into it.
TBR=tonyg@chromium.org
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8526014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109521 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=103804
TEST=this failure no longer show on GPU bots
TBR=kbr
Review URL: http://codereview.chromium.org/8527009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109520 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
TBR=antonm@chromium.org
BUG=75352
TEST=reliability tests
Review URL: http://codereview.chromium.org/8525006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109518 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Action Prediction
BUG=98110
TEST=unit_tests:NetworkActionPredictor*,interactive_ui_tests:OmniboxViewTest*
Review URL: http://codereview.chromium.org/8241014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109509 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=103759
TEST=these failures no longer showing on GPU bots
TBR=kbr
Review URL: http://codereview.chromium.org/8528003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109475 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) allow filters in webdriver tests
2) allow user to specify default Chrome to use
3) allow user to specify default driver to use
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8509024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109441 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is so that the bot does not run out of disk space
BUG=None
TEST=None
R=rdsmith@chromium.org
Review URL: http://codereview.chromium.org/8510035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109370 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
tracing feature
BUG=95714
Review URL: http://codereview.chromium.org/7982007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109368 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:19759
TEST=run_remote_test on local x86-generic VM
Change-Id: I7a1bf4061b51d134c892dca79b463621b71eb949
Review URL: http://codereview.chromium.org/8508042
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109366 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=103406
TEST=FileBrowserExtensionApiTest.*
Review URL: http://codereview.chromium.org/8495044
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109351 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/8506033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109349 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=102540
TEST=none
Review URL: http://codereview.chromium.org/8507033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109345 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
features.
The general idea is to use jbates's newly added tracing: if a feature is blacklisted, we check the tracing data to make sure gpu process hasn't launched.
BUG=101222
TEST=browser_tests
Review URL: http://codereview.chromium.org/8497034
TBR=zmo@google.com
Review URL: http://codereview.chromium.org/8510030
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109334 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
The general idea is to use jbates's newly added tracing: if a feature is blacklisted, we check the tracing data to make sure gpu process hasn't launched.
BUG=101222
TEST=browser_tests
Review URL: http://codereview.chromium.org/8497034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109328 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=98690
TEST=None
Review URL: http://codereview.chromium.org/8505038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109326 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/8510028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109321 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to InProcessBrowserTests.
InProcessBrowserTest is enough for our purpose. This change is to get ready to use a GPU BrowserTest framework where we could have more specific test expectations (like per RENDERER), and InProcessBrowserTest seems like the way to go.
Also, we simplify the test mechanism on how to report back results: from three states to a simple message.
BUG=none
TEST=gpu bots: gpu_tests
Review URL: http://codereview.chromium.org/8477048
TBR=zmo@google.com
Review URL: http://codereview.chromium.org/8506030
TBR=zmo@google.com
Review URL: http://codereview.chromium.org/8497051
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109318 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
InProcessBrowserTests.
InProcessBrowserTest is enough for our purpose. This change is to get ready to use a GPU BrowserTest framework where we could have more specific test expectations (like per RENDERER), and InProcessBrowserTest seems like the way to go.
Also, we simplify the test mechanism on how to report back results: from three states to a simple message.
BUG=none
TEST=gpu bots: gpu_tests
Review URL: http://codereview.chromium.org/8477048
TBR=zmo@google.com
Review URL: http://codereview.chromium.org/8506030
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109316 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unit_tests.
Print Preview unit_tests were good to tackle because it brought in a dependency on the need
to include another js file.
This also hilighted another need - that of being able to include non-generative js files in gyp
and have them copied to the test_data dir, while doing both generation and copy for gtest files.
I changed the "extension" of files which generate C++ with gtest-like syntax to .gtestjs and
added a copyjs rule to the chrome_tests.gypi.
FWIW, I believe this is mostly needed for unit_tests and only applied it there, although I would
be amenable to also making this change for the webui tests to make it clear that they are not
plain js files.
R=dpapad@chromium.org
BUG=101443,102222
TEST=unit_tests --gtest_filter=PrintPreviewUtilsUnitTest.*
Review URL: http://codereview.chromium.org/8438063
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109310 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
WebKit side is: https://bugs.webkit.org/show_bug.cgi?id=62284
BUG=92038
Review URL: http://codereview.chromium.org/8417055
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109266 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
R=phajdan.jr@chromium.org
TBR=phajdan.jr@chromium.org
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8505021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109262 0039d316-1c4b-4281-b951-d872f2087c98
|