BUG=chromium-os:26824
TEST=repro'd chromium-os:26790 on a test system with this config,
demonstrating that it no longer masks the bug. Confirmed
dbus-monitoring still works while doing so. (Tested with
help from jorgelo.) Confirmed the 26790 fix is not regressed by this
either.
Change-Id: I60ce833ffb14a9a709ca6bfecf40221940845aa0
Reviewed-on: https://gerrit.chromium.org/gerrit/16739
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Ready: Jim Hebert <jimhebert@chromium.org>
Tested-by: Jim Hebert <jimhebert@chromium.org>
BUG=chromium-os:23903
TEST=full build of x86-zgb, mod_for_test, boot; run dbus-monitor
on tty2 as root, log in, switch back and observe all the dbus
traffic.
Change-Id: Iccdb47bec97260108c73cf346c91c2d9e8c2bc18
Reviewed-on: https://gerrit.chromium.org/gerrit/12593
Commit-Ready: Jim Hebert <jimhebert@chromium.org>
Reviewed-by: Jim Hebert <jimhebert@chromium.org>
Tested-by: Jim Hebert <jimhebert@chromium.org>
It seems better to catch issues earlier during the build phase rather than later
during the actual test run. Prompted to do this after debugging
crosbug.com/21837.
BUG=chromium-os:23422
TEST=build_image test for x86-alex, amd64-generic, tegra2_kaen with no failures;
build_image factory_test for x86-alex with no failures; also verified that
build_image exits early with a non-zero exit code for amd64-generic without the
fix for crosbug.com/21837.
Change-Id: Ibdcf770d1d854d5a6765734556cf6ee8fc4aae96
Reviewed-on: https://gerrit.chromium.org/gerrit/12102
Tested-by: Darin Petkov <petkov@chromium.org>
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Ready: Darin Petkov <petkov@chromium.org>
BUG=chromium-os:22446
TEST=Build images and manually inspect configuration files in test and non-test
iamges.
Change-Id: I8b4ff34e40f24f1250e592e5b96d358f064610a8
Reviewed-on: https://gerrit.chromium.org/gerrit/11161
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Gary Morain <gmorain@chromium.org>
Commit-Ready: Gary Morain <gmorain@chromium.org>
It was not marked executable, and was also broken. Now updates the
CHROMEOS_RELEASE_TRACK to be testimage-channel for test images.
BUG=chromium-os:20019
TEST=Manual
Change-Id: I8741f0e21831fe3d9184ca11b73dcea96a1b01b1
Reviewed-on: http://gerrit.chromium.org/gerrit/9801
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Ready: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
It seems that the intermittent failure we see on the login screen
is due to a sort of mixed-content error, where there's a failure
within the page to load some embedded resource due to a cert error.
Make the SSL cert we inject work for any google.com server to
work around this.
BUG=chromium-os:20323
TEST=login_CryptohomeMounted 50x, suite_Smoke
Change-Id: Ic8e5b9bec799cd19cccfeddd2990fe3a494d2184
Reviewed-on: http://gerrit.chromium.org/gerrit/8818
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
test wi-fi devices.
in http://gerrit.chromium.org/gerrit/6405, we introduced support
for running some WiFi autotests in a VM (running a test image).
for those tests to work, the connection manager must not attempt
to manage the devices used by the APs.
this change adds a mod_for_test script that updates flimflam's
init script, adding command-line arguments that tell flimflam
to ignore the AP devices.
BUG=chromium-os:16348
TEST=manual: built test image, checked flimflam args in /etc/init/flimflam.conf
Change-Id: I7a26d817e78f5743e2922a35c20ad6bee139445d
Reviewed-on: http://gerrit.chromium.org/gerrit/6443
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Tested-by: mukesh agrawal <quiche@chromium.org>
The script created etc/enable_chromium_minidumps in the
stateful partition; however that file isn't on the whitelist
of stateful files that chromeos-install will install on dev
and test images.
BUG=None
TEST=install test image from USB with and without the change; observe the file is absent in both cases
Change-Id: I841cf9ed4c819a9f18cbdd11a3d42af196ab87bb
Reviewed-on: http://gerrit.chromium.org/gerrit/6354
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
This command was failing before (and the error getting swamped in log output)
resulting in a later command auto-creating the database and failing to
set the trust settings of the fake SSL cert we use in tests correctly.
BUG=chrome-os-partner:4923
TEST=build arm-generic test image, see that there are no error messages after "Generating a 1024 bit RSA private key" in the output log
Change-Id: I5b0c05d90e528aa5047cb12aa338cef176d233aa
Reviewed-on: http://gerrit.chromium.org/gerrit/5519
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
BUG=chromium-os:15989
TEST=build an image and mod it for test. See that there's no complaint about an 'Invalid Password'. Run suite_Smoke
STATUS=Fixed
Change-Id: I34bb47576ab8d5df11e79489f4996897ebf2ca3f
Reviewed-on: http://gerrit.chromium.org/gerrit/3694
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
The default is --standard_backdoor, which installs well-known ssh keys and sets
a well-known root password. Passing --nostandard_backdoor will cause
mod_image_for_test to use ssh keys from ~/.ssh/*.pub instead of the test keys
and not set the root password.
BUG=chromium-os:11744
TEST=Adhoc
Build an image with --standard_backdoor.
ssh -i ${SRC}/src/scripts/mod_for_test_scripts/ssh_keys/testing_rsa root@${DUT}
ssh root@${DUT} with 'test0000'
cat /root/.ssh/authorized_keys # check for the test key
Build an image with --nostandard_backdoor.
ssh -o PubkeyAuthentication=no root@${DUT} # this will fail
ssh root@${DUT} # this should work
cat /root/.ssh/authorized_keys # check for just your keys
Change-Id: Ie92fbc9d3815f478698c8c94d938daca2b5cd53e
Signed-off-by: Elly Jones <ellyjones@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/3449
Reviewed-by: David Rochberg <rochberg@chromium.org>
Update sed cmd to reflect multi-profile changes.
BUG=chromium-os:12948
TEST=run mod_image_for_test; boot and verify flimflam.conf is properly edited
Change-Id: I9f58aabc4c302b1e24737b0fcb15fc2719d120d6
Reviewed-on: http://gerrit.chromium.org/gerrit/1198
Tested-by: Sam Leffler <sleffler@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Various members of /dev are used (such as /dev/random) in this script,
and <() style redirection is used which requires a mounted /proc in the
image.
So bind-mount /dev and /proc while running so they work.
BUG=chromiumos:15951
TEST=examined output before/after
Change-Id: I3e8f0edef0da7e63b2af6736e8becfa1cd6d723d
Reviewed-on: http://gerrit.chromium.org/gerrit/1846
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
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
