Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 # Copyright (c) 2011 The Chromium Authors. All rights reserved. | 1 # Copyright (c) 2011 The Chromium Authors. All rights reserved. |
| 2 # Use of this source code is governed by a BSD-style license that can be | 2 # Use of this source code is governed by a BSD-style license that can be |
| 3 # found in the LICENSE file. | 3 # found in the LICENSE file. |
| 4 | 4 |
| 5 from master import gatekeeper | 5 from master import gatekeeper |
| 6 from master import master_utils | 6 from master import master_utils |
| 7 | 7 |
| 8 # This is the list of the builder categories and the corresponding critical | 8 # This is the list of the builder categories and the corresponding critical |
| 9 # steps. If one critical step fails, gatekeeper will close the tree | 9 # steps. If one critical step fails, gatekeeper will close the tree |
| 10 # automatically. | 10 # automatically. |
| 11 # Note: don't include 'update scripts' since we can't do much about it when | 11 # Note: don't include 'update scripts' since we can't do much about it when |
| 12 # it's failing and the tree is still technically fine. | 12 # it's failing and the tree is still technically fine. |
| 13 categories_steps = { | 13 categories_steps = { |
| 14 '': ['update'], | 14 '': ['update'], |
| 15 'memory_tester': [ | 15 'memory_tester': [ |
| 16 'start_crash_handler', | 16 'start_crash_handler', |
| 17 'memory test: googleurl', | 17 'memory test: googleurl', |
| 18 'memory test: printing', | 18 'memory test: printing', |
| 19 'memory test: media', | 19 'memory test: media', |
| 20 'memory test: remoting', | 20 'memory test: remoting', |
| 21 'memory test: app', | 21 'memory test: app', |
| 22 'memory test: sync_unit_tests', | 22 'memory test: sync_unit_tests', |
| 23 'memory test: ipc', | 23 'memory test: ipc', |
| 24 'memory test: base', | 24 'memory test: base', |
| 25 'memory test: crypto', | |
|
Timur Iskhodzhanov
2011/05/19 16:51:39
Be prepared to clean up the failures after restart
| |
| 25 'memory test: net', | 26 'memory test: net', |
| 26 'memory test: gfx', | 27 'memory test: gfx', |
| 27 'memory test: unit', | 28 'memory test: unit', |
| 28 'memory test: unit_1', # it's sharded on Mac Valgrind and TSan Linux | 29 'memory test: unit_1', # it's sharded on Mac Valgrind and TSan Linux |
| 29 ], | 30 ], |
| 30 'memory_ui_tester': [ | 31 'memory_ui_tester': [ |
| 31 # UI tests are flaky on the Mac Valgrind bots (http://crbug.com/51716), | 32 # UI tests are flaky on the Mac Valgrind bots (http://crbug.com/51716), |
| 32 # so we watch for UI tests only on Linux and CrOS. | 33 # so we watch for UI tests only on Linux and CrOS. |
| 33 # TODO(timurrrr): merge this with memory_tester when the issue is resolved. | 34 # TODO(timurrrr): merge this with memory_tester when the issue is resolved. |
| 34 'memory test: ui', | 35 'memory test: ui', |
| 35 'memory test: ui_1', # sharded too. | 36 'memory test: ui_1', # sharded too. |
| 36 ], | 37 ], |
| 37 'heapcheck_tester': [ | 38 'heapcheck_tester': [ |
| 38 'heapcheck test: googleurl', | 39 'heapcheck test: googleurl', |
| 39 'heapcheck test: printing', | 40 'heapcheck test: printing', |
| 40 'heapcheck test: media', | 41 'heapcheck test: media', |
| 41 'heapcheck test: courgette', | 42 'heapcheck test: courgette', |
| 42 'heapcheck test: remoting', | 43 'heapcheck test: remoting', |
| 43 'heapcheck test: app', | 44 'heapcheck test: app', |
| 44 'heapcheck test: sync_unit_tests', | 45 'heapcheck test: sync_unit_tests', |
| 45 'heapcheck test: ipc', | 46 'heapcheck test: ipc', |
| 46 'heapcheck test: base', | 47 'heapcheck test: base', |
| 48 'heapcheck test: crypto', | |
| 47 'heapcheck test: net', | 49 'heapcheck test: net', |
| 48 'heapcheck test: gfx', | 50 'heapcheck test: gfx', |
| 49 'heapcheck test: unit', | 51 'heapcheck test: unit', |
| 50 'heapcheck test: test_shell', | 52 'heapcheck test: test_shell', |
| 51 ], | 53 ], |
| 52 'windows': ['svnkill', 'taskkill'], | 54 'windows': ['svnkill', 'taskkill'], |
| 53 'compile': ['check_deps', 'compile', 'archive_build'] | 55 'compile': ['check_deps', 'compile', 'archive_build'] |
| 54 } | 56 } |
| 55 | 57 |
| 56 exclusions = { | 58 exclusions = { |
| (...skipping 17 matching lines...) Expand all Loading... | |
| 74 use_getname=True, | 76 use_getname=True, |
| 75 status_header='Failure notification for "%(steps)s" on "%(builder)s".\n' | 77 status_header='Failure notification for "%(steps)s" on "%(builder)s".\n' |
| 76 'Please see if the failures are related to your commit and take ' | 78 'Please see if the failures are related to your commit and take ' |
| 77 'appropriate actions (e.g. revert, update suppressions, notify ' | 79 'appropriate actions (e.g. revert, update suppressions, notify ' |
| 78 'sheriff, etc.).\n\n' | 80 'sheriff, etc.).\n\n' |
| 79 'For more info on the memory waterfall please see these links:\n' | 81 'For more info on the memory waterfall please see these links:\n' |
| 80 'http://dev.chromium.org/developers/how-tos/using-valgrind\n' | 82 'http://dev.chromium.org/developers/how-tos/using-valgrind\n' |
| 81 'http://dev.chromium.org/developers/tree-sheriffs/sheriff-details-chro mium/memory-sheriff' | 83 'http://dev.chromium.org/developers/tree-sheriffs/sheriff-details-chro mium/memory-sheriff' |
| 82 '\n\nBy the way, the current memory sheriff is on the CC list.' | 84 '\n\nBy the way, the current memory sheriff is on the CC list.' |
| 83 )) | 85 )) |
| OLD | NEW |