As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=c418a8f
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=be787f3
Review URL: http://codereview.chromium.org/6277015
If we are inside the chroot then we assume that the "gclient" root
is ~/trunk. If we are outside the chroot we continue with the
previous search mechanism to find the "gclient" root.
Change-Id: Ia40de609ea596228fec2644ff3046e376b112b06
BUG=chromium-os:4230
TEST=run "src/scripts/cros_overlay_list --board tegra2 --variant seaboard" inside and outside the chroot.
Review URL: http://codereview.chromium.org/6265028
As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=c418a8f
Review URL: http://codereview.chromium.org/6277015
As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Review URL: http://codereview.chromium.org/6277015
Change-Id: I9a4fc8ea0ed51a11a912f3d1c896579369fd8880
BUG=Tac0
TEST=Ran with USER=chrome-bot ./build_image and hit Ctrl+C
Review URL: http://codereview.chromium.org/6288012
As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Review URL: http://codereview.chromium.org/6277015
Previously, you could not stop working on a package if its ebuild had
been removed. This fixes this issue by skipping canonicalization if the
package name exactly matches a name in the workon file.
BUG=11214
TEST=See below.
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic list
sys-kernel/chromeos-kernel
(cros-chroot) msb@msb ~/trunk/src/scripts $ echo "=foo/bar-9999" >> ~/trunk/.config/cros_workon/x86-generic
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic list
sys-kernel/chromeos-kernel
foo/bar
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic stop foo/bar
!!! No packages matching 'foo/bar'
WARNING: error looking up package foo/bar
ERROR : Error parsing package list
*** I made changes to cros_workon here
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic list
sys-kernel/chromeos-kernel
foo/bar
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic stop foo/bar
INFO : Stopped working on 'foo/bar' for 'x86-generic'
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic list
sys-kernel/chromeos-kernel
Change-Id: Id5cbd2b145b4d0fca96cfb245f1ac99e0b3cbdf3
Review URL: http://codereview.chromium.org/6379006
We stopped using ~ in the workon files many months ago.
BUG=n0ne
TEST=See below.
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic list
sys-kernel/chromeos-kernel
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic start perf
Please run "repo sync" now.
INFO : Started working on 'dev-util/perf' for 'x86-generic'
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic list
sys-kernel/chromeos-kernel
dev-util/perf
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic stop perf
INFO : Stopped working on 'dev-util/perf' for 'x86-generic'
(cros-chroot) msb@msb ~/trunk/src/scripts $ ./cros_workon --board x86-generic list
sys-kernel/chromeos-kernel
Change-Id: I61babd89073d749111be7257b2e8491f07ca52f2
Review URL: http://codereview.chromium.org/6268012
Change-Id: I666296627fc87910903b0a4c3f9bcfd7362daa41
BUG=n0ne
TEST=Verify they are not in the developer workflow
Review URL: http://codereview.chromium.org/6287010
dump output until after the command has finished, so not useful for
following 'live'.
Change-Id: Ia8562f5e6f8d7ed8af7e188faa68f5cdbba487c6
BUG=chromium-os:11164
TEST=None
Review URL: http://codereview.chromium.org/6296013
image_to_live runs dev_server with sudo so old cached entries are
owned by root rather than $USER. Change to pre-generate also with
sudo.
Change-Id: I587f15953b37d4de439977e7dbac9fced175c173
BUG=chromium-os:10723
TEST=Ran it
Review URL: http://codereview.chromium.org/6380008
fix, but it leads to better error messages from ctest.
Change-Id: I624ad805ef037b022e6e67b56f0ed10ca05fe325
BUG=11096
TEST=Test currently in progress.
Review URL: http://codereview.chromium.org/6257007
First CL of many. Thought I'd commit this before the others since
it sets stuff up for the other CL's (i.e. Thread Pool).
With this CL, all updates will be pre-generated before the test run.
This should improve some speeds since the two updates will be produced
at the same time rather than at the time of the sequential tests.
Change-Id: Iaf0a06f0d99c31d3d749e478fd2fb6efa0763a28
BUG=chromium-os:10723
TEST=Ran it with -q
Review URL: http://codereview.chromium.org/6264005
The last entry from the commands output will always be the one that we
want. By using this we also avoid having to tack on -private and hope
that people who created the overlay conformed to that naming convention.
BUG=NA
TEST=prebuilt_unittest updated and run
Review URL: http://codereview.chromium.org/6348010
build problems, and will give better diagnostics if not.
Change-Id: I2f7a5d9b2e0c63a8189ad212125c7a5c0178c3c4
BUG=10567
TEST=
Review URL: http://codereview.chromium.org/6331007
to eventually moving entirely out of the overlay directory. The reason
to do this now is to avoid devs having to remerge there make.conf changes
while they are in flight.
Add private support to prebuilt.py so we will update private overlays if
we are internal and external if we are external.
Update prebuilt_unittest to ensure we are returning the proper path if
the private overlay exists. Also ensure we are returning the proper host
path regardless.
BUG=9919
TEST=unittest added for private case
This reverts commit ea621903e9.
TEST=grep dmesg for clock & nmi to make sure things look ok.
Run example program to make sure result of clock_getres call tv_nsec = 1 again
BUG=chromium-os:10720
Change-Id: Ife23fc7d08420788d4c165957d739ec2ce974969
Review URL: http://codereview.chromium.org/6274006
This is take 2 of this CL. Modified run_remote_test.sh to
explicitly start an ssh-agent if necessary instead of
implicitly relying on remote_access.sh to do it.
BUG=n0ne
TEST=Verified I could successfully ssh.
Change-Id: I4e70b8574af1119dcf36768f6602ecc0cabedc31
Review URL: http://codereview.chromium.org/6288004
run_remote_test.sh is implicitly depending on remote_access.sh to setup
the ssh-agent for it. This broke when I tried to remove ssh-agent starting
from remote-access.sh. Implicitly dependencies are ugly.
BUG=n0ne
TEST=Ran a test on my local machine. Tested with and without default board.
Change-Id: I50db1717cafc2565cb8bb648919430d9ce24ce80
Review URL: http://codereview.chromium.org/6333001
Change-Id: I046d49c7002586671dc7c6707afeeeb0a0360cd5
BUG=10934
TEST=Ran it with bin/cros_mark_chrome_as_stable tot. Verified output and that it still did the right thing
Review URL: http://codereview.chromium.org/6327002
The last CL had a race condition where we could ping but not run the reboot_check code.
This CL moves to watch the reboot_check code rather than a ping.
Change-Id: I8bdda97850ac085be9cf5dfb0b80fb7e1c8dd212
BUG=chromium-os:10867
TEST=Ran it 100 times without error.
Review URL: http://codereview.chromium.org/6287001
When running outside chroot, we should use locate_cgpt + "$GPT" to invoke cgpt;
otherwise it may be not in system PATH.
For dealing with a true SSD image (over USB, for example) this CL also improved
data writing speed from <2M/s to 8M/s+ (over USB).
BUG=chromium-os:10531
TEST=./make_factory_package.sh \
--factory=../build/images/x86-mario/latest/chromiumos_factory_image.bin \
--release=../build/images/x86-mario/latest//chromiumos_image.bin \
--diskimg=/dev/sdb
Also tested:
--diskimg=blah # local file
(chroot) --diskimg=/dev/sdd
(chroot) --diskimg=blah
Change-Id: I647d97fe388f5b6a6223fa8cacfecdf00265f60c
Review URL: http://codereview.chromium.org/6261003
Since there's a pushd call when building images, we have to first retrieve
the complete (full/absolute) path of target disk image.
BUG=chromium-os:10706
TEST=make_factory_package.sh \
--factory ../build/images/x86-mario/latest/factory_image.bin \
--release ../build/images/x86-mario/latest/chromiumos_image.bin \
--diskimg blah_relative.bin
Change-Id: I02e2edb0f76b724337a82dd400297877681bc338
Review URL: http://codereview.chromium.org/6244003
Upon investigation it seems there's a race condition when ssh
starts up the first time. This adds a much more robust way to
ping a machine when it's up then the previous method.
Change-Id: I092744b259c169975d1c4f283f01a556fce24723
BUG=chromium-os:10867
TEST=Ran it 30 times with image_to_live --noupdate --nostateful_update.
Review URL: http://codereview.chromium.org/6115009
ARM (kernel-next) should now be in sync with kernel.git so that we get similar
error handling behavior on all targeted platforms (with our partition layout).
This change makes that the default.
BUG=chromium-os:9697
TEST=manual build_image with kernel-next profile; booted and validated failover error behavior
Change-Id: I281302adb3cbc96aa5770630898f103b0d3639ca
Review URL: http://codereview.chromium.org/6220002
This cleanup code consolidates parsing of options, removes
globals, cleans up private vs. public functions, removes the backup full update option, and cleans up
docstrings.
Change-Id: I3eba26b3634fd87f4a36f195ab42ec7bd11e963f
BUG=chromium-os:8901
TEST=Ran with prefix SimpleTest and ran whole suite for a vm using my latest built image. Also ran normal update test using latest image against latest dev channel image for mario. Re-tested with new changes after build break.
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=2b2d7a1
Review URL: http://codereview.chromium.org/6015013
