AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5e11777a06
skia2/infra/bots/recipes/test.expected/Test-Android-Clang-Nexus5x-GPU-Adreno418-arm-Debug-All-Android_ASAN.json

1047 lines
52 KiB
JSON
Raw Normal View History

temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
[
[recipes] Remove core.setup() Each recipe now includes its own setup steps. Bug: skia:6473 Change-Id: I97eab2cd63f5004c07408e844cbbed735aac355f Reviewed-on: https://skia-review.googlesource.com/125660 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-04 17:46:15 +00:00
{
"cmd": [
"python",
"-u",
"RECIPE_MODULE[recipe_engine::file]/resources/fileutil.py",
"--json-output",
"/path/to/tmp/json",
"ensure-directory",
"--mode",
"0777",
"[START_DIR]/tmp"
],
"infra_step": true,
"name": "makedirs tmp_dir"
},
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"mkdir",
"-p",
"/sdcard/revenge_of_the_skiabot/resources"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "mkdir /sdcard/revenge_of_the_skiabot/resources"
},
{
"cmd": [
"python",
"-u",
Make ASAN setup of Android bots more fault tolerant Bug: skia:7975 Change-Id: I3f123337913870a921d1c09714873eaf2949e88f Reviewed-on: https://skia-review.googlesource.com/129364 Commit-Queue: Kevin Lubick <kjlubick@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-21 19:47:14 +00:00
"\nimport os\nimport subprocess\nimport sys\nimport time\nADB = sys.argv[1]\nASAN_SETUP = sys.argv[2]\n\ndef wait_for_device():\n while True:\n time.sleep(5)\n print 'Waiting for device'\n subprocess.check_output([ADB, 'wait-for-device'])\n bit1 = subprocess.check_output([ADB, 'shell', 'getprop',\n 'dev.bootcomplete'])\n bit2 = subprocess.check_output([ADB, 'shell', 'getprop',\n 'sys.boot_completed'])\n if '1' in bit1 and '1' in bit2:\n print 'Device detected'\n break\n\nlog = subprocess.check_output([ADB, 'root'])\n# check for message like 'adbd cannot run as root in production builds'\nprint log\nif 'cannot' in log:\n raise Exception('adb root failed')\n\noutput = subprocess.check_output([ADB, 'disable-verity'])\nprint output\n\nif 'already disabled' not in output:\n print 'Rebooting device'\n subprocess.check_output([ADB, 'reboot'])\n wait_for_device()\n\ndef installASAN(revert=False):\n # ASAN setup script is idempotent, either it installs it or\n # says it's installed. Returns True on success, false otherwise.\n out = subprocess.check_output([ADB, 'wait-for-device'])\n print out\n cmd = [ASAN_SETUP]\n if revert:\n cmd = [ASAN_SETUP, '--revert']\n process = subprocess.Popen(cmd, env={'ADB': ADB},\n stdout=subprocess.PIPE, stderr=subprocess.PIPE)\n\n # this also blocks until command finishes\n (stdout, stderr) = process.communicate()\n print stdout\n print 'Stderr: %s' % stderr\n return process.returncode == 0\n\nif not installASAN():\n print 'Trying to revert the ASAN install and then re-install'\n # ASAN script sometimes has issues if it was interrupted or partially applied\n # Try reverting it, then re-enabling it\n if not installASAN(revert=True):\n raise Exception('reverting ASAN install failed')\n\n # Sleep because device does not reboot instantly\n time.sleep(10)\n\n if not installASAN():\n raise Exception('Tried twice to setup ASAN and failed.')\n\n# Sleep because device does not reboot instantly\ntime.sleep(10)\nwait_for_device()\n",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"/opt/infra-android/tools/adb",
asan_device_setup has moved Change-Id: I9d9d34f1b663a06605eddeacd945517c3e880f4f Reviewed-on: https://skia-review.googlesource.com/128016 Reviewed-by: Brian Osman <brianosman@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-05-14 19:20:05 +00:00
"[START_DIR]/android_ndk_linux/toolchains/llvm/prebuilt/linux-x86_64/lib64/clang/6.0.2/bin/asan_device_setup"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "Setting up device to run ASAN",
"timeout": 300,
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@import time@@@",
"@@@STEP_LOG_LINE@python.inline@ADB = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@ASAN_SETUP = sys.argv[2]@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@def wait_for_device():@@@",
"@@@STEP_LOG_LINE@python.inline@ while True:@@@",
"@@@STEP_LOG_LINE@python.inline@ time.sleep(5)@@@",
"@@@STEP_LOG_LINE@python.inline@ print 'Waiting for device'@@@",
"@@@STEP_LOG_LINE@python.inline@ subprocess.check_output([ADB, 'wait-for-device'])@@@",
"@@@STEP_LOG_LINE@python.inline@ bit1 = subprocess.check_output([ADB, 'shell', 'getprop',@@@",
"@@@STEP_LOG_LINE@python.inline@ 'dev.bootcomplete'])@@@",
"@@@STEP_LOG_LINE@python.inline@ bit2 = subprocess.check_output([ADB, 'shell', 'getprop',@@@",
"@@@STEP_LOG_LINE@python.inline@ 'sys.boot_completed'])@@@",
"@@@STEP_LOG_LINE@python.inline@ if '1' in bit1 and '1' in bit2:@@@",
"@@@STEP_LOG_LINE@python.inline@ print 'Device detected'@@@",
"@@@STEP_LOG_LINE@python.inline@ break@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@log = subprocess.check_output([ADB, 'root'])@@@",
"@@@STEP_LOG_LINE@python.inline@# check for message like 'adbd cannot run as root in production builds'@@@",
"@@@STEP_LOG_LINE@python.inline@print log@@@",
"@@@STEP_LOG_LINE@python.inline@if 'cannot' in log:@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('adb root failed')@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@output = subprocess.check_output([ADB, 'disable-verity'])@@@",
"@@@STEP_LOG_LINE@python.inline@print output@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@if 'already disabled' not in output:@@@",
"@@@STEP_LOG_LINE@python.inline@ print 'Rebooting device'@@@",
"@@@STEP_LOG_LINE@python.inline@ subprocess.check_output([ADB, 'reboot'])@@@",
"@@@STEP_LOG_LINE@python.inline@ wait_for_device()@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
Make ASAN setup of Android bots more fault tolerant Bug: skia:7975 Change-Id: I3f123337913870a921d1c09714873eaf2949e88f Reviewed-on: https://skia-review.googlesource.com/129364 Commit-Queue: Kevin Lubick <kjlubick@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-21 19:47:14 +00:00
"@@@STEP_LOG_LINE@python.inline@def installASAN(revert=False):@@@",
"@@@STEP_LOG_LINE@python.inline@ # ASAN setup script is idempotent, either it installs it or@@@",
"@@@STEP_LOG_LINE@python.inline@ # says it's installed. Returns True on success, false otherwise.@@@",
"@@@STEP_LOG_LINE@python.inline@ out = subprocess.check_output([ADB, 'wait-for-device'])@@@",
"@@@STEP_LOG_LINE@python.inline@ print out@@@",
"@@@STEP_LOG_LINE@python.inline@ cmd = [ASAN_SETUP]@@@",
"@@@STEP_LOG_LINE@python.inline@ if revert:@@@",
"@@@STEP_LOG_LINE@python.inline@ cmd = [ASAN_SETUP, '--revert']@@@",
"@@@STEP_LOG_LINE@python.inline@ process = subprocess.Popen(cmd, env={'ADB': ADB},@@@",
"@@@STEP_LOG_LINE@python.inline@ stdout=subprocess.PIPE, stderr=subprocess.PIPE)@@@",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"@@@STEP_LOG_LINE@python.inline@@@@",
Make ASAN setup of Android bots more fault tolerant Bug: skia:7975 Change-Id: I3f123337913870a921d1c09714873eaf2949e88f Reviewed-on: https://skia-review.googlesource.com/129364 Commit-Queue: Kevin Lubick <kjlubick@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-21 19:47:14 +00:00
"@@@STEP_LOG_LINE@python.inline@ # this also blocks until command finishes@@@",
"@@@STEP_LOG_LINE@python.inline@ (stdout, stderr) = process.communicate()@@@",
"@@@STEP_LOG_LINE@python.inline@ print stdout@@@",
"@@@STEP_LOG_LINE@python.inline@ print 'Stderr: %s' % stderr@@@",
"@@@STEP_LOG_LINE@python.inline@ return process.returncode == 0@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@if not installASAN():@@@",
"@@@STEP_LOG_LINE@python.inline@ print 'Trying to revert the ASAN install and then re-install'@@@",
"@@@STEP_LOG_LINE@python.inline@ # ASAN script sometimes has issues if it was interrupted or partially applied@@@",
"@@@STEP_LOG_LINE@python.inline@ # Try reverting it, then re-enabling it@@@",
"@@@STEP_LOG_LINE@python.inline@ if not installASAN(revert=True):@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('reverting ASAN install failed')@@@",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@ # Sleep because device does not reboot instantly@@@",
Make ASAN setup of Android bots more fault tolerant Bug: skia:7975 Change-Id: I3f123337913870a921d1c09714873eaf2949e88f Reviewed-on: https://skia-review.googlesource.com/129364 Commit-Queue: Kevin Lubick <kjlubick@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-21 19:47:14 +00:00
"@@@STEP_LOG_LINE@python.inline@ time.sleep(10)@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@ if not installASAN():@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('Tried twice to setup ASAN and failed.')@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@# Sleep because device does not reboot instantly@@@",
"@@@STEP_LOG_LINE@python.inline@time.sleep(10)@@@",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"@@@STEP_LOG_LINE@python.inline@wait_for_device()@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nhost = sys.argv[1]\ndevice = sys.argv[2]\nfor d, _, fs in os.walk(host):\n p = os.path.relpath(d, host)\n if p != '.' and p.startswith('.'):\n continue\n for f in fs:\n print os.path.join(p,f)\n subprocess.check_call(['/opt/infra-android/tools/adb', 'push',\n os.path.realpath(os.path.join(host, p, f)),\n os.path.join(device, p, f)])\n",
"[START_DIR]/skia/resources",
"/sdcard/revenge_of_the_skiabot/resources"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "push [START_DIR]/skia/resources/* /sdcard/revenge_of_the_skiabot/resources",
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@host = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@device = sys.argv[2]@@@",
"@@@STEP_LOG_LINE@python.inline@for d, _, fs in os.walk(host):@@@",
"@@@STEP_LOG_LINE@python.inline@ p = os.path.relpath(d, host)@@@",
"@@@STEP_LOG_LINE@python.inline@ if p != '.' and p.startswith('.'):@@@",
"@@@STEP_LOG_LINE@python.inline@ continue@@@",
"@@@STEP_LOG_LINE@python.inline@ for f in fs:@@@",
"@@@STEP_LOG_LINE@python.inline@ print os.path.join(p,f)@@@",
"@@@STEP_LOG_LINE@python.inline@ subprocess.check_call(['/opt/infra-android/tools/adb', 'push',@@@",
"@@@STEP_LOG_LINE@python.inline@ os.path.realpath(os.path.join(host, p, f)),@@@",
"@@@STEP_LOG_LINE@python.inline@ os.path.join(device, p, f)])@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"RECIPE_MODULE[recipe_engine::file]/resources/fileutil.py",
"--json-output",
"/path/to/tmp/json",
"copy",
"[START_DIR]/skia/infra/bots/assets/skp/VERSION",
"/path/to/tmp/"
],
"infra_step": true,
[recipes] Add asset_version utility function. Bug: skia:7720 Change-Id: I044ca5281354b21c9deffa408ad7ec20c51d2e2e Reviewed-on: https://skia-review.googlesource.com/115122 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Ben Wagner <benjaminwagner@google.com>
2018-03-19 20:52:37 +00:00
"name": "Get skp VERSION"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
{
"cmd": [
"python",
"-u",
"RECIPE_MODULE[recipe_engine::file]/resources/fileutil.py",
"--json-output",
"/path/to/tmp/json",
"copy",
"42",
"[START_DIR]/tmp/SKP_VERSION"
],
"infra_step": true,
"name": "write SKP_VERSION"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"cat",
"/sdcard/revenge_of_the_skiabot/SKP_VERSION"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "read /sdcard/revenge_of_the_skiabot/SKP_VERSION",
"stdout": "/path/to/tmp/"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"rm",
"-f",
"/sdcard/revenge_of_the_skiabot/SKP_VERSION"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "rm /sdcard/revenge_of_the_skiabot/SKP_VERSION"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"rm",
"-rf",
"/sdcard/revenge_of_the_skiabot/skps"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "rm /sdcard/revenge_of_the_skiabot/skps"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"mkdir",
"-p",
"/sdcard/revenge_of_the_skiabot/skps"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "mkdir /sdcard/revenge_of_the_skiabot/skps"
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nhost = sys.argv[1]\ndevice = sys.argv[2]\nfor d, _, fs in os.walk(host):\n p = os.path.relpath(d, host)\n if p != '.' and p.startswith('.'):\n continue\n for f in fs:\n print os.path.join(p,f)\n subprocess.check_call(['/opt/infra-android/tools/adb', 'push',\n os.path.realpath(os.path.join(host, p, f)),\n os.path.join(device, p, f)])\n",
"[START_DIR]/skp",
"/sdcard/revenge_of_the_skiabot/skps"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "push [START_DIR]/skp/* /sdcard/revenge_of_the_skiabot/skps",
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@host = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@device = sys.argv[2]@@@",
"@@@STEP_LOG_LINE@python.inline@for d, _, fs in os.walk(host):@@@",
"@@@STEP_LOG_LINE@python.inline@ p = os.path.relpath(d, host)@@@",
"@@@STEP_LOG_LINE@python.inline@ if p != '.' and p.startswith('.'):@@@",
"@@@STEP_LOG_LINE@python.inline@ continue@@@",
"@@@STEP_LOG_LINE@python.inline@ for f in fs:@@@",
"@@@STEP_LOG_LINE@python.inline@ print os.path.join(p,f)@@@",
"@@@STEP_LOG_LINE@python.inline@ subprocess.check_call(['/opt/infra-android/tools/adb', 'push',@@@",
"@@@STEP_LOG_LINE@python.inline@ os.path.realpath(os.path.join(host, p, f)),@@@",
"@@@STEP_LOG_LINE@python.inline@ os.path.join(device, p, f)])@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"push",
"[START_DIR]/tmp/SKP_VERSION",
"/sdcard/revenge_of_the_skiabot/SKP_VERSION"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "push [START_DIR]/tmp/SKP_VERSION /sdcard/revenge_of_the_skiabot/SKP_VERSION"
},
{
"cmd": [
"python",
"-u",
"RECIPE_MODULE[recipe_engine::file]/resources/fileutil.py",
"--json-output",
"/path/to/tmp/json",
"copy",
"[START_DIR]/skia/infra/bots/assets/skimage/VERSION",
"/path/to/tmp/"
],
"infra_step": true,
[recipes] Add asset_version utility function. Bug: skia:7720 Change-Id: I044ca5281354b21c9deffa408ad7ec20c51d2e2e Reviewed-on: https://skia-review.googlesource.com/115122 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Ben Wagner <benjaminwagner@google.com>
2018-03-19 20:52:37 +00:00
"name": "Get skimage VERSION"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
{
"cmd": [
"python",
"-u",
"RECIPE_MODULE[recipe_engine::file]/resources/fileutil.py",
"--json-output",
"/path/to/tmp/json",
"copy",
"42",
"[START_DIR]/tmp/SK_IMAGE_VERSION"
],
"infra_step": true,
"name": "write SK_IMAGE_VERSION"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"cat",
"/sdcard/revenge_of_the_skiabot/SK_IMAGE_VERSION"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "read /sdcard/revenge_of_the_skiabot/SK_IMAGE_VERSION",
"stdout": "/path/to/tmp/"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"rm",
"-f",
"/sdcard/revenge_of_the_skiabot/SK_IMAGE_VERSION"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "rm /sdcard/revenge_of_the_skiabot/SK_IMAGE_VERSION"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"rm",
"-rf",
"/sdcard/revenge_of_the_skiabot/images"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "rm /sdcard/revenge_of_the_skiabot/images"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"mkdir",
"-p",
"/sdcard/revenge_of_the_skiabot/images"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "mkdir /sdcard/revenge_of_the_skiabot/images"
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nhost = sys.argv[1]\ndevice = sys.argv[2]\nfor d, _, fs in os.walk(host):\n p = os.path.relpath(d, host)\n if p != '.' and p.startswith('.'):\n continue\n for f in fs:\n print os.path.join(p,f)\n subprocess.check_call(['/opt/infra-android/tools/adb', 'push',\n os.path.realpath(os.path.join(host, p, f)),\n os.path.join(device, p, f)])\n",
"[START_DIR]/skimage",
"/sdcard/revenge_of_the_skiabot/images"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "push [START_DIR]/skimage/* /sdcard/revenge_of_the_skiabot/images",
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@host = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@device = sys.argv[2]@@@",
"@@@STEP_LOG_LINE@python.inline@for d, _, fs in os.walk(host):@@@",
"@@@STEP_LOG_LINE@python.inline@ p = os.path.relpath(d, host)@@@",
"@@@STEP_LOG_LINE@python.inline@ if p != '.' and p.startswith('.'):@@@",
"@@@STEP_LOG_LINE@python.inline@ continue@@@",
"@@@STEP_LOG_LINE@python.inline@ for f in fs:@@@",
"@@@STEP_LOG_LINE@python.inline@ print os.path.join(p,f)@@@",
"@@@STEP_LOG_LINE@python.inline@ subprocess.check_call(['/opt/infra-android/tools/adb', 'push',@@@",
"@@@STEP_LOG_LINE@python.inline@ os.path.realpath(os.path.join(host, p, f)),@@@",
"@@@STEP_LOG_LINE@python.inline@ os.path.join(device, p, f)])@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"push",
"[START_DIR]/tmp/SK_IMAGE_VERSION",
"/sdcard/revenge_of_the_skiabot/SK_IMAGE_VERSION"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "push [START_DIR]/tmp/SK_IMAGE_VERSION /sdcard/revenge_of_the_skiabot/SK_IMAGE_VERSION"
},
{
"cmd": [
"python",
"-u",
"RECIPE_MODULE[recipe_engine::file]/resources/fileutil.py",
"--json-output",
"/path/to/tmp/json",
"copy",
"[START_DIR]/skia/infra/bots/assets/svg/VERSION",
"/path/to/tmp/"
],
"infra_step": true,
[recipes] Add asset_version utility function. Bug: skia:7720 Change-Id: I044ca5281354b21c9deffa408ad7ec20c51d2e2e Reviewed-on: https://skia-review.googlesource.com/115122 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Ben Wagner <benjaminwagner@google.com>
2018-03-19 20:52:37 +00:00
"name": "Get svg VERSION"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
{
"cmd": [
"python",
"-u",
"RECIPE_MODULE[recipe_engine::file]/resources/fileutil.py",
"--json-output",
"/path/to/tmp/json",
"copy",
"42",
"[START_DIR]/tmp/SVG_VERSION"
],
"infra_step": true,
"name": "write SVG_VERSION"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"cat",
"/sdcard/revenge_of_the_skiabot/SVG_VERSION"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "read /sdcard/revenge_of_the_skiabot/SVG_VERSION",
"stdout": "/path/to/tmp/"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"rm",
"-f",
"/sdcard/revenge_of_the_skiabot/SVG_VERSION"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "rm /sdcard/revenge_of_the_skiabot/SVG_VERSION"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"rm",
"-rf",
"/sdcard/revenge_of_the_skiabot/svgs"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "rm /sdcard/revenge_of_the_skiabot/svgs"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"shell",
"mkdir",
"-p",
"/sdcard/revenge_of_the_skiabot/svgs"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "mkdir /sdcard/revenge_of_the_skiabot/svgs"
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nhost = sys.argv[1]\ndevice = sys.argv[2]\nfor d, _, fs in os.walk(host):\n p = os.path.relpath(d, host)\n if p != '.' and p.startswith('.'):\n continue\n for f in fs:\n print os.path.join(p,f)\n subprocess.check_call(['/opt/infra-android/tools/adb', 'push',\n os.path.realpath(os.path.join(host, p, f)),\n os.path.join(device, p, f)])\n",
"[START_DIR]/svg",
"/sdcard/revenge_of_the_skiabot/svgs"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "push [START_DIR]/svg/* /sdcard/revenge_of_the_skiabot/svgs",
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@host = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@device = sys.argv[2]@@@",
"@@@STEP_LOG_LINE@python.inline@for d, _, fs in os.walk(host):@@@",
"@@@STEP_LOG_LINE@python.inline@ p = os.path.relpath(d, host)@@@",
"@@@STEP_LOG_LINE@python.inline@ if p != '.' and p.startswith('.'):@@@",
"@@@STEP_LOG_LINE@python.inline@ continue@@@",
"@@@STEP_LOG_LINE@python.inline@ for f in fs:@@@",
"@@@STEP_LOG_LINE@python.inline@ print os.path.join(p,f)@@@",
"@@@STEP_LOG_LINE@python.inline@ subprocess.check_call(['/opt/infra-android/tools/adb', 'push',@@@",
"@@@STEP_LOG_LINE@python.inline@ os.path.realpath(os.path.join(host, p, f)),@@@",
"@@@STEP_LOG_LINE@python.inline@ os.path.join(device, p, f)])@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"push",
"[START_DIR]/tmp/SVG_VERSION",
"/sdcard/revenge_of_the_skiabot/SVG_VERSION"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "push [START_DIR]/tmp/SVG_VERSION /sdcard/revenge_of_the_skiabot/SVG_VERSION"
},
{
"cmd": [
"python",
"-u",
"import os\nprint os.environ.get('SWARMING_BOT_ID', '')\n"
],
"name": "get swarming bot id",
"stdout": "/path/to/tmp/",
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@print os.environ.get('SWARMING_BOT_ID', '')@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"import os\nprint os.environ.get('SWARMING_TASK_ID', '')\n"
],
"name": "get swarming task id",
"stdout": "/path/to/tmp/",
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@print os.environ.get('SWARMING_TASK_ID', '')@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nimport time\nADB = sys.argv[1]\ncpu = int(sys.argv[2])\nvalue = int(sys.argv[3])\n\nlog = subprocess.check_output([ADB, 'root'])\n# check for message like 'adbd cannot run as root in production builds'\nprint log\nif 'cannot' in log:\n raise Exception('adb root failed')\n\n# If we try to echo 1 to an already online cpu, adb returns exit code 1.\n# So, check the value before trying to write it.\nprior_status = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()\nif prior_status == str(value):\n print 'CPU %d online already %d' % (cpu, value)\n sys.exit()\n\nsubprocess.check_output([ADB, 'shell', 'echo %s > '\n '/sys/devices/system/cpu/cpu%d/online' % (value, cpu)])\nactual_status = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()\nif actual_status != str(value):\n raise Exception('(actual, expected) (%s, %d)'\n % (actual_status, value))\n",
"/opt/infra-android/tools/adb",
"0",
"1"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "Enabling CPU 0",
"timeout": 30,
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@import time@@@",
"@@@STEP_LOG_LINE@python.inline@ADB = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@cpu = int(sys.argv[2])@@@",
"@@@STEP_LOG_LINE@python.inline@value = int(sys.argv[3])@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@log = subprocess.check_output([ADB, 'root'])@@@",
"@@@STEP_LOG_LINE@python.inline@# check for message like 'adbd cannot run as root in production builds'@@@",
"@@@STEP_LOG_LINE@python.inline@print log@@@",
"@@@STEP_LOG_LINE@python.inline@if 'cannot' in log:@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('adb root failed')@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@# If we try to echo 1 to an already online cpu, adb returns exit code 1.@@@",
"@@@STEP_LOG_LINE@python.inline@# So, check the value before trying to write it.@@@",
"@@@STEP_LOG_LINE@python.inline@prior_status = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if prior_status == str(value):@@@",
"@@@STEP_LOG_LINE@python.inline@ print 'CPU %d online already %d' % (cpu, value)@@@",
"@@@STEP_LOG_LINE@python.inline@ sys.exit()@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@subprocess.check_output([ADB, 'shell', 'echo %s > '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % (value, cpu)])@@@",
"@@@STEP_LOG_LINE@python.inline@actual_status = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if actual_status != str(value):@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('(actual, expected) (%s, %d)'@@@",
"@@@STEP_LOG_LINE@python.inline@ % (actual_status, value))@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nimport time\nADB = sys.argv[1]\ncpu = int(sys.argv[2])\nvalue = int(sys.argv[3])\n\nlog = subprocess.check_output([ADB, 'root'])\n# check for message like 'adbd cannot run as root in production builds'\nprint log\nif 'cannot' in log:\n raise Exception('adb root failed')\n\n# If we try to echo 1 to an already online cpu, adb returns exit code 1.\n# So, check the value before trying to write it.\nprior_status = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()\nif prior_status == str(value):\n print 'CPU %d online already %d' % (cpu, value)\n sys.exit()\n\nsubprocess.check_output([ADB, 'shell', 'echo %s > '\n '/sys/devices/system/cpu/cpu%d/online' % (value, cpu)])\nactual_status = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()\nif actual_status != str(value):\n raise Exception('(actual, expected) (%s, %d)'\n % (actual_status, value))\n",
"/opt/infra-android/tools/adb",
"1",
"1"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "Enabling CPU 1",
"timeout": 30,
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@import time@@@",
"@@@STEP_LOG_LINE@python.inline@ADB = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@cpu = int(sys.argv[2])@@@",
"@@@STEP_LOG_LINE@python.inline@value = int(sys.argv[3])@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@log = subprocess.check_output([ADB, 'root'])@@@",
"@@@STEP_LOG_LINE@python.inline@# check for message like 'adbd cannot run as root in production builds'@@@",
"@@@STEP_LOG_LINE@python.inline@print log@@@",
"@@@STEP_LOG_LINE@python.inline@if 'cannot' in log:@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('adb root failed')@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@# If we try to echo 1 to an already online cpu, adb returns exit code 1.@@@",
"@@@STEP_LOG_LINE@python.inline@# So, check the value before trying to write it.@@@",
"@@@STEP_LOG_LINE@python.inline@prior_status = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if prior_status == str(value):@@@",
"@@@STEP_LOG_LINE@python.inline@ print 'CPU %d online already %d' % (cpu, value)@@@",
"@@@STEP_LOG_LINE@python.inline@ sys.exit()@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@subprocess.check_output([ADB, 'shell', 'echo %s > '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % (value, cpu)])@@@",
"@@@STEP_LOG_LINE@python.inline@actual_status = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if actual_status != str(value):@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('(actual, expected) (%s, %d)'@@@",
"@@@STEP_LOG_LINE@python.inline@ % (actual_status, value))@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nimport time\nADB = sys.argv[1]\ncpu = int(sys.argv[2])\nvalue = int(sys.argv[3])\n\nlog = subprocess.check_output([ADB, 'root'])\n# check for message like 'adbd cannot run as root in production builds'\nprint log\nif 'cannot' in log:\n raise Exception('adb root failed')\n\n# If we try to echo 1 to an already online cpu, adb returns exit code 1.\n# So, check the value before trying to write it.\nprior_status = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()\nif prior_status == str(value):\n print 'CPU %d online already %d' % (cpu, value)\n sys.exit()\n\nsubprocess.check_output([ADB, 'shell', 'echo %s > '\n '/sys/devices/system/cpu/cpu%d/online' % (value, cpu)])\nactual_status = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()\nif actual_status != str(value):\n raise Exception('(actual, expected) (%s, %d)'\n % (actual_status, value))\n",
"/opt/infra-android/tools/adb",
"2",
"1"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "Enabling CPU 2",
"timeout": 30,
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@import time@@@",
"@@@STEP_LOG_LINE@python.inline@ADB = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@cpu = int(sys.argv[2])@@@",
"@@@STEP_LOG_LINE@python.inline@value = int(sys.argv[3])@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@log = subprocess.check_output([ADB, 'root'])@@@",
"@@@STEP_LOG_LINE@python.inline@# check for message like 'adbd cannot run as root in production builds'@@@",
"@@@STEP_LOG_LINE@python.inline@print log@@@",
"@@@STEP_LOG_LINE@python.inline@if 'cannot' in log:@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('adb root failed')@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@# If we try to echo 1 to an already online cpu, adb returns exit code 1.@@@",
"@@@STEP_LOG_LINE@python.inline@# So, check the value before trying to write it.@@@",
"@@@STEP_LOG_LINE@python.inline@prior_status = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if prior_status == str(value):@@@",
"@@@STEP_LOG_LINE@python.inline@ print 'CPU %d online already %d' % (cpu, value)@@@",
"@@@STEP_LOG_LINE@python.inline@ sys.exit()@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@subprocess.check_output([ADB, 'shell', 'echo %s > '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % (value, cpu)])@@@",
"@@@STEP_LOG_LINE@python.inline@actual_status = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if actual_status != str(value):@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('(actual, expected) (%s, %d)'@@@",
"@@@STEP_LOG_LINE@python.inline@ % (actual_status, value))@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nimport time\nADB = sys.argv[1]\ncpu = int(sys.argv[2])\nvalue = int(sys.argv[3])\n\nlog = subprocess.check_output([ADB, 'root'])\n# check for message like 'adbd cannot run as root in production builds'\nprint log\nif 'cannot' in log:\n raise Exception('adb root failed')\n\n# If we try to echo 1 to an already online cpu, adb returns exit code 1.\n# So, check the value before trying to write it.\nprior_status = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()\nif prior_status == str(value):\n print 'CPU %d online already %d' % (cpu, value)\n sys.exit()\n\nsubprocess.check_output([ADB, 'shell', 'echo %s > '\n '/sys/devices/system/cpu/cpu%d/online' % (value, cpu)])\nactual_status = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()\nif actual_status != str(value):\n raise Exception('(actual, expected) (%s, %d)'\n % (actual_status, value))\n",
"/opt/infra-android/tools/adb",
"3",
"1"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "Enabling CPU 3",
"timeout": 30,
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@import time@@@",
"@@@STEP_LOG_LINE@python.inline@ADB = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@cpu = int(sys.argv[2])@@@",
"@@@STEP_LOG_LINE@python.inline@value = int(sys.argv[3])@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@log = subprocess.check_output([ADB, 'root'])@@@",
"@@@STEP_LOG_LINE@python.inline@# check for message like 'adbd cannot run as root in production builds'@@@",
"@@@STEP_LOG_LINE@python.inline@print log@@@",
"@@@STEP_LOG_LINE@python.inline@if 'cannot' in log:@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('adb root failed')@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@# If we try to echo 1 to an already online cpu, adb returns exit code 1.@@@",
"@@@STEP_LOG_LINE@python.inline@# So, check the value before trying to write it.@@@",
"@@@STEP_LOG_LINE@python.inline@prior_status = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if prior_status == str(value):@@@",
"@@@STEP_LOG_LINE@python.inline@ print 'CPU %d online already %d' % (cpu, value)@@@",
"@@@STEP_LOG_LINE@python.inline@ sys.exit()@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@subprocess.check_output([ADB, 'shell', 'echo %s > '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % (value, cpu)])@@@",
"@@@STEP_LOG_LINE@python.inline@actual_status = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/online' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if actual_status != str(value):@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('(actual, expected) (%s, %d)'@@@",
"@@@STEP_LOG_LINE@python.inline@ % (actual_status, value))@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nimport time\nADB = sys.argv[1]\ncpu = int(sys.argv[2])\ngov = sys.argv[3]\n\nlog = subprocess.check_output([ADB, 'root'])\n# check for message like 'adbd cannot run as root in production builds'\nprint log\nif 'cannot' in log:\n raise Exception('adb root failed')\n\nsubprocess.check_output([ADB, 'shell', 'echo \"%s\" > '\n '/sys/devices/system/cpu/cpu%d/cpufreq/scaling_governor' % (gov, cpu)])\nactual_gov = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/cpufreq/scaling_governor' % cpu]).strip()\nif actual_gov != gov:\n raise Exception('(actual, expected) (%s, %s)'\n % (actual_gov, gov))\n",
"/opt/infra-android/tools/adb",
"4",
"ondemand"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "Set CPU 4's governor to ondemand",
"timeout": 30,
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@import time@@@",
"@@@STEP_LOG_LINE@python.inline@ADB = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@cpu = int(sys.argv[2])@@@",
"@@@STEP_LOG_LINE@python.inline@gov = sys.argv[3]@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@log = subprocess.check_output([ADB, 'root'])@@@",
"@@@STEP_LOG_LINE@python.inline@# check for message like 'adbd cannot run as root in production builds'@@@",
"@@@STEP_LOG_LINE@python.inline@print log@@@",
"@@@STEP_LOG_LINE@python.inline@if 'cannot' in log:@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('adb root failed')@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@subprocess.check_output([ADB, 'shell', 'echo \"%s\" > '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/cpufreq/scaling_governor' % (gov, cpu)])@@@",
"@@@STEP_LOG_LINE@python.inline@actual_gov = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/cpufreq/scaling_governor' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if actual_gov != gov:@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('(actual, expected) (%s, %s)'@@@",
"@@@STEP_LOG_LINE@python.inline@ % (actual_gov, gov))@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nimport time\nADB = sys.argv[1]\ncpu = int(sys.argv[2])\ngov = sys.argv[3]\n\nlog = subprocess.check_output([ADB, 'root'])\n# check for message like 'adbd cannot run as root in production builds'\nprint log\nif 'cannot' in log:\n raise Exception('adb root failed')\n\nsubprocess.check_output([ADB, 'shell', 'echo \"%s\" > '\n '/sys/devices/system/cpu/cpu%d/cpufreq/scaling_governor' % (gov, cpu)])\nactual_gov = subprocess.check_output([ADB, 'shell', 'cat '\n '/sys/devices/system/cpu/cpu%d/cpufreq/scaling_governor' % cpu]).strip()\nif actual_gov != gov:\n raise Exception('(actual, expected) (%s, %s)'\n % (actual_gov, gov))\n",
"/opt/infra-android/tools/adb",
"0",
"ondemand"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "Set CPU 0's governor to ondemand",
"timeout": 30,
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@import time@@@",
"@@@STEP_LOG_LINE@python.inline@ADB = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@cpu = int(sys.argv[2])@@@",
"@@@STEP_LOG_LINE@python.inline@gov = sys.argv[3]@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@log = subprocess.check_output([ADB, 'root'])@@@",
"@@@STEP_LOG_LINE@python.inline@# check for message like 'adbd cannot run as root in production builds'@@@",
"@@@STEP_LOG_LINE@python.inline@print log@@@",
"@@@STEP_LOG_LINE@python.inline@if 'cannot' in log:@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('adb root failed')@@@",
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@subprocess.check_output([ADB, 'shell', 'echo \"%s\" > '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/cpufreq/scaling_governor' % (gov, cpu)])@@@",
"@@@STEP_LOG_LINE@python.inline@actual_gov = subprocess.check_output([ADB, 'shell', 'cat '@@@",
"@@@STEP_LOG_LINE@python.inline@ '/sys/devices/system/cpu/cpu%d/cpufreq/scaling_governor' % cpu]).strip()@@@",
"@@@STEP_LOG_LINE@python.inline@if actual_gov != gov:@@@",
"@@@STEP_LOG_LINE@python.inline@ raise Exception('(actual, expected) (%s, %s)'@@@",
"@@@STEP_LOG_LINE@python.inline@ % (actual_gov, gov))@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"push",
Reland [recipes] Isolate build outputs with no subdirs Bug: skia:6473 Change-Id: I730cb860abc72473aaa9af98527fd220b9a55120 Reviewed-on: https://skia-review.googlesource.com/131389 Reviewed-by: Ben Wagner <benjaminwagner@google.com> Commit-Queue: Eric Boren <borenet@google.com>
2018-06-01 14:08:53 +00:00
"[START_DIR]/build/dm",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"/data/local/tmp/"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "push dm"
},
{
"cmd": [
"python",
"-u",
"RECIPE_MODULE[recipe_engine::file]/resources/fileutil.py",
"--json-output",
"/path/to/tmp/json",
"copy",
Update GPU DM/nanobench configs for color testing - Rename '*srgbnl' to '*srgb'. - Add '*narrow' and '*enarrow' for testing a gamut narrower than sRGB. - Stopped blacklisting glessrgb. It no longer uses sRGB pixel configs, so should work fine on all GPUs. - Also runs 'esrgb' (F16 sRGB) everywhere. This is likely to fail on some devices that have poor (or no) F16 support. Change-Id: I941d0758adb3b0c895c7a8a85ff0ae4aa5bff6e7 Reviewed-on: https://skia-review.googlesource.com/136171 Commit-Queue: Brian Osman <brianosman@google.com> Reviewed-by: Brian Salomon <bsalomon@google.com> Reviewed-by: Mike Klein <mtklein@google.com>
2018-06-20 18:53:06 +00:00
"set -x; /data/local/tmp/dm --resourcePath /sdcard/revenge_of_the_skiabot/resources --skps /sdcard/revenge_of_the_skiabot/skps --images /sdcard/revenge_of_the_skiabot/images/dm --colorImages /sdcard/revenge_of_the_skiabot/images/colorspace --nameByHash --properties gitHash abc123 builder Test-Android-Clang-Nexus5x-GPU-Adreno418-arm-Debug-All-Android_ASAN buildbucket_build_id 123454321 swarming_bot_id skia-bot-123 swarming_task_id 123456 --svgs /sdcard/revenge_of_the_skiabot/svgs --key arch arm compiler Clang configuration Debug cpu_or_gpu GPU cpu_or_gpu_value Adreno418 extra_config Android_ASAN model Nexus5x os Android --dont_write pdf --nocpu --config gles glesdft glessrgb glesesrgb glesmsaa4 --src tests gm image colorImage svg --blacklist _ svg _ svgparse_ glessrgb image _ _ _ test _ GrShape _ image _ interlaced1.png _ image _ interlaced2.png _ image _ interlaced3.png _ image _ .arw _ image _ .cr2 _ image _ .dng _ image _ .nef _ image _ .nrw _ image _ .orf _ image _ .raf _ image _ .rw2 _ image _ .pef _ image _ .srw _ image _ .ARW _ image _ .CR2 _ image _ .DNG _ image _ .NEF _ image _ .NRW _ image _ .ORF _ image _ .RAF _ image _ .RW2 _ image _ .PEF _ image _ .SRW _ gm _ encode-platform --match ~BadImage --noRAW_threading --nonativeFonts --verbose; echo $? >/data/local/tmp/rc",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"[START_DIR]/tmp/dm.sh"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "write dm.sh"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"push",
"[START_DIR]/tmp/dm.sh",
"/data/local/tmp/"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "push dm.sh"
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"logcat",
"-c"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "clear log"
},
{
"cmd": [
"python",
"-u",
"\nimport subprocess\nimport sys\nbin_dir = sys.argv[1]\nsh = sys.argv[2]\nsubprocess.check_call(['/opt/infra-android/tools/adb', 'shell', 'sh', bin_dir + sh])\ntry:\n sys.exit(int(subprocess.check_output(['/opt/infra-android/tools/adb', 'shell', 'cat',\n bin_dir + 'rc'])))\nexcept ValueError:\n print \"Couldn't read the return code. Probably killed for OOM.\"\n sys.exit(1)\n",
"/data/local/tmp/",
"dm.sh"
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"name": "dm",
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@bin_dir = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@sh = sys.argv[2]@@@",
"@@@STEP_LOG_LINE@python.inline@subprocess.check_call(['/opt/infra-android/tools/adb', 'shell', 'sh', bin_dir + sh])@@@",
"@@@STEP_LOG_LINE@python.inline@try:@@@",
"@@@STEP_LOG_LINE@python.inline@ sys.exit(int(subprocess.check_output(['/opt/infra-android/tools/adb', 'shell', 'cat',@@@",
"@@@STEP_LOG_LINE@python.inline@ bin_dir + 'rc'])))@@@",
"@@@STEP_LOG_LINE@python.inline@except ValueError:@@@",
"@@@STEP_LOG_LINE@python.inline@ print \"Couldn't read the return code. Probably killed for OOM.\"@@@",
"@@@STEP_LOG_LINE@python.inline@ sys.exit(1)@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"python",
"-u",
"\nimport os\nimport subprocess\nimport sys\nout = sys.argv[1]\nlog = subprocess.check_output(['/opt/infra-android/tools/adb', 'logcat', '-d'])\nfor line in log.split('\\n'):\n tokens = line.split()\n if len(tokens) == 11 and tokens[-7] == 'F' and tokens[-3] == 'pc':\n addr, path = tokens[-2:]\n local = os.path.join(out, os.path.basename(path))\n if os.path.exists(local):\n sym = subprocess.check_output(['addr2line', '-Cfpe', local, addr])\n line = line.replace(addr, addr + ' ' + sym.strip())\n print line\n",
Reland [recipes] Isolate build outputs with no subdirs Bug: skia:6473 Change-Id: I730cb860abc72473aaa9af98527fd220b9a55120 Reviewed-on: https://skia-review.googlesource.com/131389 Reviewed-by: Ben Wagner <benjaminwagner@google.com> Commit-Queue: Eric Boren <borenet@google.com>
2018-06-01 14:08:53 +00:00
"[START_DIR]/build"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
],
"env": {
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "dump log",
"timeout": 300,
"~followup_annotations": [
"@@@STEP_LOG_LINE@python.inline@@@@",
"@@@STEP_LOG_LINE@python.inline@import os@@@",
"@@@STEP_LOG_LINE@python.inline@import subprocess@@@",
"@@@STEP_LOG_LINE@python.inline@import sys@@@",
"@@@STEP_LOG_LINE@python.inline@out = sys.argv[1]@@@",
"@@@STEP_LOG_LINE@python.inline@log = subprocess.check_output(['/opt/infra-android/tools/adb', 'logcat', '-d'])@@@",
"@@@STEP_LOG_LINE@python.inline@for line in log.split('\\n'):@@@",
"@@@STEP_LOG_LINE@python.inline@ tokens = line.split()@@@",
"@@@STEP_LOG_LINE@python.inline@ if len(tokens) == 11 and tokens[-7] == 'F' and tokens[-3] == 'pc':@@@",
"@@@STEP_LOG_LINE@python.inline@ addr, path = tokens[-2:]@@@",
"@@@STEP_LOG_LINE@python.inline@ local = os.path.join(out, os.path.basename(path))@@@",
"@@@STEP_LOG_LINE@python.inline@ if os.path.exists(local):@@@",
"@@@STEP_LOG_LINE@python.inline@ sym = subprocess.check_output(['addr2line', '-Cfpe', local, addr])@@@",
"@@@STEP_LOG_LINE@python.inline@ line = line.replace(addr, addr + ' ' + sym.strip())@@@",
"@@@STEP_LOG_LINE@python.inline@ print line@@@",
"@@@STEP_LOG_END@python.inline@@@"
]
},
{
"cmd": [
"/opt/infra-android/tools/adb",
"kill-server"
],
"cwd": "[START_DIR]/skia",
"env": {
Specify the ADB keys to use for ADB In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
2018-05-17 18:35:43 +00:00
"ADB_VENDOR_KEYS": "/home/chrome-bot/.android/chrome_infrastructure_adbkey",
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
"CHROME_HEADLESS": "1",
[recipes] BUILDTYPE and SKIA_OUT are no longer used Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
2018-05-15 19:04:58 +00:00
"PATH": "<PATH>:RECIPE_PACKAGE_REPO[depot_tools]"
temporarily disable BadImage test on new ASAN bot Here's the current error: ==6835==WARNING: AddressSanitizer failed to allocate 0xc0000028 bytes ==6835==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6835==If you don't like this behavior set allocator_may_return_null=1 ==6835==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 "((0)) != (0)" (0x0, 0x0) Looking at how sk_malloc and co all funnel into sk_malloc_flags(), and how our local sk_malloc_flags() works, I think everything would be fine to run this bot with allocator_may_return_null=1, but I'm not sure how to do that. Change-Id: I155439e17dd6353b82056de12f49de34e9538643 Reviewed-on: https://skia-review.googlesource.com/101660 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-01-30 13:08:49 +00:00
},
"infra_step": true,
"name": "kill adb server"
},
{
"name": "$result",
"recipe_result": null,
"status_code": 0
}
]
Reference in New Issue Copy Permalink