New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 665509 link

Starred by 3 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Configure GCE instances to support nesting and run VMTest

Project Member Reported by nxia@chromium.org, Nov 15 2016

Issue description

As a part of moving physical builders to GCE builders, we need to run VMTest in GCE VMs.

The nesting feature is still being tested by the GCE team. In order to run VMTest on GCE, need to setup a whitelisted VM and attach a license shared from the GCE team.
 

Comment 1 by nxia@chromium.org, Nov 18 2016

Successfully exported an image and attached the license. when I tried to created an image with the licensed_image.tar.gz, the operation failed with the error " - The size of the image inside the tar archive is larger than 100 Gb.".

After consulting the GCE team, finally decided to go over all the processes again without using the trusty-image we used for our build, instead, pick up a smaller image and attach the license. Expecting the new instance to support Cbuildbot. 

Comment 2 by nxia@chromium.org, Nov 18 2016

Created a test instance with the license imported. Tried to run Cbuildbot with VMTest, it turned out it required environment configured by buildbot steps, I made some tweaks, it failed in different places though.

will:
1) continue on working out the Cbuildbot.
2) learn manual vmtest steps suggested by Don.

Comment 3 by nxia@chromium.org, Nov 21 2016

Triggered a cbuildbot run and vmtest first failed with package_not_installed error. installed the packages and run vmtest individually (as cbuildbot has prepared all the prerequisites). Looks like vmtest passed:

nxia@kvm-test-6-builder:/mnt/tmp/buildroot/src/scripts$ bin/ctest '--board=cyan' '--type=vm' --no_graphics --verbose '--target_image=/mnt/tmp/buildroot/src/build/images/cyan/latest-cbuildbot/chromiumos_test_image.bin' '--test_results_root=/mnt/tmp/buildroot/chroot/tmp/cbuildbotrsua0_/test_harness' --only_verify '--suite=smoke' --whitelist_chrome_crashes '--ssh_private_key=/mnt/tmp/buildroot/src/build/images/cyan/latest-cbuildbot/id_rsa' 
2016/11/19 01:34:46 - ctest - INFO    : Could not find a latest image to use. Using target instead.
2016/11/19 01:34:46 - cros_build_lib.py - INFO    : RunCommand: /mnt/tmp/buildroot/src/platform/crostestutils/au_test_harness/cros_au_test_harness.py '--base_image=/mnt/tmp/buildroot/src/build/images/cyan/latest-cbuildbot/chromiumos_test_image.bin' '--target_image=/mnt/tmp/buildroot/src/build/images/cyan/latest-cbuildbot/chromiumos_test_image.bin' '--board=cyan' '--type=vm' '--remote=0.0.0.0' --verbose '--jobs=1' '--ssh_private_key=/mnt/tmp/buildroot/src/build/images/cyan/latest-cbuildbot/id_rsa' '--verify_suite_name=smoke' '--test_prefix=SimpleTestVerify' '--test_results_root=/mnt/tmp/buildroot/chroot/tmp/cbuildbotrsua0_/test_harness' --no_graphics --whitelist_chrome_crashes in /mnt/tmp/buildroot/src/scripts
2016/11/19 01:34:46 - cros_au_test_harness.py - INFO    : No update cache found. Update testing will not work.  Run  cros_generate_update_payloads if this was not intended.
2016/11/19 01:34:46 - cros_au_test_harness.py - INFO    : Running tests in test suite in parallel.
2016/11/19 01:36:30 - au_worker.py - INFO    : SimpleTestVerify: Copied shared disk image /mnt/tmp/buildroot/src/build/images/cyan/latest-cbuildbot/chromiumos_qemu_image.bin to /tmp/chromiumos_qemu_disk.bin.zHCQb_.
2016/11/19 01:36:30 - au_worker.py - INFO    : SimpleTestVerify: Running smoke suite to verify image.
INFO    : QEMU binary: /mnt/tmp/buildroot/chroot/usr/bin/qemu-system-x86_64
INFO    : QEMU version: QEMU emulator version 2.6.0, Copyright (c) 2003-2008 Fabrice Bellard
Stopping the KVM instance
.
----------------------------------------------------------------------
Ran 1 test in 1314.800s

OK

Comment 4 by nxia@chromium.org, Nov 23 2016

uploaded results to gs://kvm-bucket/vmtest_result.tar

Comment 5 by nxia@chromium.org, Nov 30 2016

Cc: dgarr...@chromium.org
The result logs look good to me. @dgarrett, Can you just confirm the tests passed without problems?
Sweet! That OK at the end is the sign of goodness.

The other way to check is the exit code (echo $?), which is what cbuildbot does.

Comment 7 by nxia@chromium.org, Dec 14 2016

Status: Fixed (was: Untriaged)

Comment 8 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 9 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 10 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 11 by nxia@chromium.org, Jun 21 2017

Cc: sosa@chromium.org nxia@chromium.org abw@chromium.org d...@chromium.org zelidrag@chromium.org
 Issue 341900  has been merged into this issue.
Labels: VerifyIn-61

Comment 13 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment