[Findit] Set up android_chromium_variable_nexus4 to use dedicated bot with device |
|||
Issue descriptionandroid_chromium_variable_nexus4 uses the ccompute_optional_bots slave pool which does not have dedicated devices, required for running tests. Thus all test try jobs for master chromium.webkit builder "WebKit Android (Nexus4)" fail due to device_status_check exceptions. Need to point android_chromium_variable_nexus4 to a buildslave that is guaranteed to have a device attached
,
Apr 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build.git/+/0cb45d4f3c200d53bf93d7db53e4c936f6ff05ca commit 0cb45d4f3c200d53bf93d7db53e4c936f6ff05ca Author: lijeffrey@chromium.org <lijeffrey@chromium.org> Date: Fri Apr 22 23:51:19 2016 Adding new pool with dedicated nexus4 device For Findit to trigger test try jobs correctly against WebKit Android (Nexus4), a bot with a dedicated device is needed. Without it test tryjobs will fail due to device_status_check exceptions. This change points the variable builder to a pool with a dedicated slave with device. BUG= 606007 Review URL: https://codereview.chromium.org/1912243002 git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/build@300126 0039d316-1c4b-4281-b951-d872f2087c98 [modify] https://crrev.com/0cb45d4f3c200d53bf93d7db53e4c936f6ff05ca/masters/master.tryserver.chromium.android/builders.pyl
,
Apr 25 2016
,
Apr 25 2016
Now that the new bot is set up and running not_run_tests from this master/builder's trybot config has been removed. |
|||
►
Sign in to add a comment |
|||
Comment 1 by st...@chromium.org
, Apr 22 2016