diff options
| author | dpranke@chromium.org <dpranke@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-08-20 14:36:59 +0000 |
|---|---|---|
| committer | dpranke@chromium.org <dpranke@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-08-20 14:36:59 +0000 |
| commit | f9e7ddb6668fcf422ef3ee92309e8f657c3c0640 (patch) | |
| tree | c77bf62b5e248ace0582dd3a48fc1bb056c8eaf2 /build/android | |
| parent | 8b3e3d8f101deab32cc3482ad752e99802efe109 (diff) | |
| download | chromium_src-f9e7ddb6668fcf422ef3ee92309e8f657c3c0640.zip chromium_src-f9e7ddb6668fcf422ef3ee92309e8f657c3c0640.tar.gz chromium_src-f9e7ddb6668fcf422ef3ee92309e8f657c3c0640.tar.bz2 | |
Make failing webkit_tests fail android build.
Now that r156332 has landed in theory, the webkit_tests step should pass
(since we're only running one test), and we should start trying to figure
out how reliable the bots actually are.
This change flips the bot config so that a failing webkit_tests step will
cause the build to be red. If this turns out to be premature, I'll revert
this change, but we should start gathering real data on what does and doesn't
work now.
R=ilevy@chromium.org, mbulach@chromium.org
BUG=232044
Review URL: https://chromiumcodereview.appspot.com/23242008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218489 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build/android')
| -rwxr-xr-x | build/android/buildbot/bb_device_steps.py | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/build/android/buildbot/bb_device_steps.py b/build/android/buildbot/bb_device_steps.py index f020281..260ec76 100755 --- a/build/android/buildbot/bb_device_steps.py +++ b/build/android/buildbot/bb_device_steps.py @@ -223,8 +223,7 @@ def RunWebkitLayoutTests(options): cmd_args.extend( ['--additional-expectations=%s' % os.path.join(CHROME_SRC, *f)]) - RunCmd(['webkit/tools/layout_tests/run_webkit_tests.py'] + cmd_args, - flunk_on_failure=False) + RunCmd(['webkit/tools/layout_tests/run_webkit_tests.py'] + cmd_args) def SpawnLogcatMonitor(): |