Additional change for the relocation of Autotest from /home/autotest to /usr/local/autotest. See http://codereview.chromium.org/6090004/
Change-Id: Id6f7ac6e93124414b0b6c6bed48efccfd982a49d
BUG=chromium-os:10799
TEST=Will test as whole with rest of /usr/local changes.
Review URL: http://codereview.chromium.org/5972012
We were snaking core dumps out from under the crash reporter on test images, and no one was even using them. We'd like to leverage the crash reporter to detect that crashes happened during a test run, so disable this.
BUG=7936
TEST=spin up a VM, send SEGV to chrome. crash_reporter messages should appear in /var/log/messages
Change-Id: Icc2be55616ac931ca3ec1a7810ea3e09a006a26b
Review URL: http://codereview.chromium.org/4019006
Change-Id: I51df060627770d88c219501bc628e91229ac0d42
BUG=7286
TEST=Boot in mod_for_test, home is mounted exec
Review URL: http://codereview.chromium.org/3529021
BUG=chromium-os:6204
TEST=Ran mod_image_for_test.sh, mounted resulting image and verfied
disable_idle_suspend now shows up under /usr/share/power_manager
instead of /var/lib/power_manager
Change-Id: Ia34787b364cd5ffa199efc4a36b5d9d691a33c5a
Review URL: http://codereview.chromium.org/3326011
This change must accompany http://codereview.chromium.org/3330005/show
Change-Id: If57a726933e4a243e424bdc98ddd577081afe6e2
BUG=chromium-os:6345
TEST=manual
built an image, ran mod_image_for_test on it, then
split the image into partition blobs, mounted part_3 and
checked /etc/init/{openssh-server,iptables,saft}.conf
- they all have the #for_test string removed.
removed.
Review URL: http://codereview.chromium.org/3309006
pam_google used to install /etc/login_trust_root.pem, and then this script would
modify it. We no longer install pam_google, so we need to create this file
de-novo now.
BUG=None
TEST=build_image, then mod for test. Check that /etc/login_trust_root.pem exists, contains one cert, and has the right permissions. For maximum goodness, run login_LoginSuccess
Change-Id: I409ffeea4b30905cf9e0506650b67556fa5ec80e
Review URL: http://codereview.chromium.org/3185024
BUG=5130
TEST=create a test image, boot it on a device, and run "sudo nsscertutil -d "sql:/etc/fake_root_ca/nssdb" -L -n FakeCert | less". Look at the section of the output marked "Validity:" and make sure the Not Before and Not After sections indicate dates that are 3 weeks apart
Change-Id: I67cf7e71027147f83c1bc916557bc06ef66fa0e0
Review URL: http://codereview.chromium.org/3075025
mod_image_for_test.sh now passes the target architecture to the subscripts
mod_for_test_scripts/710enableAuthTesting generates the /etc/fake_root_cert
databases by running nsscertutil under QEMU.
BUG=3310
TEST=Built autotest enabled images for x86 and arm. On arm, the browser no
longer crashes trying to read the fake root certs.
Review URL: http://codereview.chromium.org/2878033
power_LoadTest will use this symlink to load a test extension at login.
BUG=None
TEST=power_LoadTest
Signed-off-by: Benson Leung <bleung@chromium.org>
Review URL: http://codereview.chromium.org/2877007
to handle changed command line arguments, and attempt
to make it resilient in the face of future changes.
TEST=Run script on fresh image; confirm that '-I eth_test' is present on the exec line of /etc/init/flimflam.conf
Review URL: http://codereview.chromium.org/2842023
This prevents the machine from suspending while it is being tested.
TEST=Modified an image for test and verified that powerd did not suspend.
BUG=chromium-os:3694
Review URL: http://codereview.chromium.org/2620008
BUG=3283
TEST=Tested by running mod_image_for_test and checking the stateful partiton
on the resulting image and verifying that these files exist in the correct
locations.
Review URL: http://codereview.chromium.org/2107013
on the device under test and to use a not-normally-generated interface name, so that use of add-on ethernet devices is not affected in normal operation.
BUG=2962, 2941
(dup of 1810013, git goofiness)
Review URL: http://codereview.chromium.org/1826003
After discussing with drewry, we can't come up with a better way to inject these root certs. We considered putting them on the stateful partition, but that opens up an avenue of attack (if you can get a root cert into the magic directory, then you can MITM login). Thus, we put it on the rootfs instead. The script that sets up the hashes for vboot will verify that this directory is not present in production images. That work is tracked here: http://code.google.com/p/chromium-os/issues/detail?id=2693
Review URL: http://codereview.chromium.org/1566055
It worked when all mod for test script works inside chroot. But not anymore since "df /" now report the host disk space, not the rootfs.
Review URL: http://codereview.chromium.org/1130005
Get rid of chroot inside this script, and not mounting mod_for_test_scripts into rootfs any more.
The reason caused the failure here is once you chroot into the mounted rootfs directory, all binaries were searched inside the rootfs. But all binaries inside the arm rootfs was for arm hardware, so not executable on the host linux machine(intel).
Review URL: http://codereview.chromium.org/845007
- Rev chromeos-systemtests, and add fio as a dependency.
- Add fio into the image during mod_image_for_test.sh
Review URL: http://chromereview.prom.corp.google.com/1180028
git-svn-id: svn://chrome-svn/chromeos/trunk@297 06c00378-0e64-4dae-be16-12b19f9950a1
