Test stage for chromeos-chrome bot |
||||||||
Issue descriptionchrome-tot-chromeos-amd64-generic builder: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/chrome-tot-chromeos-amd64-generic The config file for this is in build_internal/scripts/slave/recipe_modules/chrome/chromeos_chrome.py This needs a 'tests' step. The tests step needs to call cros_run_vm_tests --disable-kvm --deploy --build-dir=out_amd64-generic/Release We can drop the --disable-kvm when GCE supports KVM.
,
May 19 2017
,
May 21 2017
,
May 25 2017
I spoke to achuith@ about what we'd need to do to get this working as part of the Chromium CQ. For starters, we'd want trybots configured that match the waterfall bot configuration, and we don't currently have those. The "easiest" way to do that may be to switch them from using the "chromeos" recipe to the "chromium" recipe, and at first glance that may not be *that* hard, since we do have builders for similar configs that use the chromium recipe, e.g.: https://build.chromium.org/p/chromium.chromiumos/builders/ChromiumOS%20amd64-generic%20Compile https://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_amd64-generic_chromium_compile_only_ng apart from the generic configuration above, adding a specific test step to run the test locally on the builder shouldn't be too hard. The real target needs to be to run the test under swarming, though, and that's going to take more work, as we need to isolate everything that cros_sdk and cros_run_vm_tests sets up in the environment and make sure that it is included in the bundle and sent over to the swarming bot. This shouldn't be particularly hard, but it will take some trial and error, I expect.
,
May 30 2017
,
May 31 2017
,
Feb 23 2018
,
Feb 23 2018
,
Sep 18
We're now running tests in the chrome cq |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by achuith@chromium.org
, May 19 2017