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

Issue 598375 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

results_dir_root failure in cros_run_vm_test

Project Member Reported by achuith@chromium.org, Mar 28 2016

Issue description

./cros_run_vm_test --board=x86-generic --image_path=../../build/images/x86-generic/latest/chromiumos_qemu_image.bin login_Cryptohome


I get this:

Starting a KVM instance
INFO    : KVM started with pid stored in /tmp/kvm.13510.pid
INFO    : Serial output, if available, can be found here in /tmp/kvm.13510.serial
Builder uptime:  15:57:15 up 1:18, 11 users, load average: 0.62, 0.27, 0.25
Builder meminfo:
MemTotal:       65901608 kB
MemFree:        59124272 kB
Buffers:          320940 kB
Cached:          3375180 kB
SwapCached:            0 kB
Active:          3324944 kB
Inactive:        2425988 kB
Active(anon):    2089152 kB
Inactive(anon):    61216 kB
Active(file):    1235792 kB
Inactive(file):  2364772 kB
Unevictable:       34088 kB
Mlocked:           34088 kB
SwapTotal:      67031036 kB
SwapFree:       67031036 kB
Dirty:               720 kB
Writeback:             0 kB
AnonPages:       2123776 kB
Mapped:           470528 kB
Shmem:             62520 kB
Slab:             332644 kB
SReclaimable:     234664 kB
SUnreclaim:        97980 kB
KernelStack:       14840 kB
PageTables:        45748 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    99981840 kB
Committed_AS:   11441344 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      466732 kB
VmallocChunk:   34325142908 kB
HardwareCorrupted:     0 kB
AnonHugePages:   1112064 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:      310252 kB
DirectMap2M:     8003584 kB
DirectMap1G:    58720256 kB
usage: test_that.py [-h] [-w WEB] [-x MAX_RUNTIME_MINS] [--fast] [--args ARGS]
                    [--results_dir RESULTS_DIR] [--pretend]
                    [--no-experimental] [--enforce-deps] [--debug]
                    [--iterations ITERATIONS] [--ssh_verbosity {0,1,2,3}]
                    [--ssh_options SSH_OPTIONS] [-b BOARD] [-i BUILD]
                    [-p POOL] [--autotest_dir AUTOTEST_DIR] [--no-quickmerge]
                    [--whitelist-chrome-crashes]
                    [--ssh_private_key SSH_PRIVATE_KEY]
                    REMOTE TEST [TEST ...]

 
https://cs.corp.google.com/chromeos_public/src/platform/crostestutils/cros_run_vm_test?l=102

Looks like results-dir was deprecated from test_that at some point?
Oops, I left out the actual error line:
test_that.py: error: argument --results_dir: expected one argument

Summary: results_dir_root failure in cros_run_vm_test (was: results-dir failure in cros_run_vm_test)
Actually just adding --results_dir_root=/var/tmp/foo fixed this. The error reporting should be better.
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 29 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/crostestutils/+/27afe00632dac8ecfa8b2330b5f88341d80ce85b

commit 27afe00632dac8ecfa8b2330b5f88341d80ce85b
Author: Achuith Bhandarkar <achuith@chromium.org>
Date: Mon Mar 28 18:53:44 2016

die if --results_root_dir is not specified.

BUG= chromium:598375 
TEST=manual

Change-Id: I5d9b0d9806585d209912305028c0807d25117a8b
Reviewed-on: https://chromium-review.googlesource.com/335630
Commit-Ready: Achuith Bhandarkar <achuith@chromium.org>
Tested-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>

[modify] https://crrev.com/27afe00632dac8ecfa8b2330b5f88341d80ce85b/cros_run_vm_test

Labels: -Proj-PFQCodeYellow Hotlist-CrOS-Gardener
Owner: achuith@chromium.org
Status: Assigned (was: Untriaged)
Relabling Hotlist-CrOS-Gardener - we're using the PFQCodeYellow label to track top level tracking bugs.

Status: Fixed (was: Assigned)

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

Labels: VerifyIn-59

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

Labels: VerifyIn-60

Comment 9 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

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

Status: Archived (was: Fixed)

Sign in to add a comment