To get best factory test image performance, we should disable update engine.
BUG=chromium-os:13613
TEST=image_to_usb --factory --to=FACTORY
then verified /etc/init/update-engine.conf is disabled.
Change-Id: Ifb7b6c821f434ee68625ffea0eb7907c38d77315
R=nsanders@chromium.org
Review URL: http://codereview.chromium.org/6759023
BUG=none
TEST=Run ChromeOS under qemu, the screen should be 1280x1024 not 800x600.
Review URL: http://codereview.chromium.org/6768009
Change-Id: I9a73025244a85d3b07e98136b373b00bb40cd9dd
to the output of images uploaded to Google Storage. This is a stop gap solution
until I migrate all builders to uploading with the new structure.
BUG=NA
TEST=Ran on a finished buildbot to ensure the proper behaviour
Review URL: http://codereview.chromium.org/6749018
Change-Id: I52901180e962c463bdaacbc573f93700cf9ab4bd
BUG=None
TEST=Run Chrome OS in qemu, check that the mouse is back.
Review URL: http://codereview.chromium.org/6749020
Moved this incorrectly. This is only used by
cros_vm_lib.sh and therefore should stay wherever it is.
Change-Id: Ib9cc02479f53184a85345288f6abd8fedffb563e
BUG=chromium-os:13948
TEST=NA
Review URL: http://codereview.chromium.org/6747015
Change-Id: Id0fa142e0e4705e0ec742dd2c926687140507dc4
BUG=chromium-os:13498
TEST=Ran other CL's without this file.
Review URL: http://codereview.chromium.org/6713120
BUG=chromium-os:13221
TEST=Run build_images without ext2 loaded
Specifying a filesystem type explicitly for ext* filesystems will avoid
weird fallbacks like mounting ext2 filesystem as ext3 or even ext4.
Instead it attempts to autoload the given filesystem as a module if
available or fail right away.
Change-Id: I6be7f3f994babd8efc8eda97ea9c802e04d98be6
R=dgarret@chromium.org,sosa@chromium.org
Review URL: http://codereview.chromium.org/6696092
For run_remote_tests this required "fixing" restart_in_chroot if required. Right now that script ->only<- works if its run on a scripts being called from src/scripts. This change makes it more generic by doing this for any script called from within our source tree.
I borrow reinterpret_path_for_chroot from image_to_live. Other CL to remove it from there.
Change-Id: If717beccd777ac178366d58b91521b9a62d55d85
BUG=chromium-os:11172
TEST=Ran them
Review URL: http://codereview.chromium.org/6730012
Change-Id: I8233aaab234eb6a3a7948abb1d311c4c9c162190
BUG=chromium-os:11172
TEST=Ran from new symlinks from previous locations.
Review URL: http://codereview.chromium.org/6731005
This also deletes the code from mod_for_factory_scripts/200patchInitScript
that created the files that now come from the new package.
BUG=chromium-os:13258
TEST=Build and boot a factory test image
Review URL: http://codereview.chromium.org/6665048
Change-Id: I115d1a2e3afe2fdefc0e07247b21b67e0cf9cc62
BUG=none
TEST=build and boot a factory test image
Review URL: http://codereview.chromium.org/6713049
Change-Id: Ia0c4c9780fccc91c4464acf84ca4c0327b8ea7bd
This CL removes --factory_install support from mod_image_for_test.
Factory install images are no longer produced using mod_image_for_test.
BUG=chromium-os:12899
TEST=manual
Change-Id: Ia6d6cac07f710cb82473fd696c2717ee660543b6
Review URL: http://codereview.chromium.org/6688015
The dev install shim is deprecated. This CL removes --dev_install
support from build_image.
This is part of a larger rewrite of build_image to allow it to be the
single script from which all image types are generated.
BUG=chromium-os:12899
TEST=manual
Change-Id: Ic3a49f0d476d198f81001a05c75f24f16bc640c0
Review URL: http://codereview.chromium.org/6694042
This should fix the failure seen in internal builds
Change-Id: I527acc37597ab9157aedf0330e43f3159ee66fdd
BUG=Should exist
TEST=Ran it locally
TBR=dgarret. Internal builds have been failing on these for a while and no one yelled about it :(
Review URL: http://codereview.chromium.org/6676059
Cleaned up _InsertKeyIntoImage to be more general (able to remove key if no key set). Also made it much more intelligent ... only doing things when it needs to.
Moved mount / unmount code to cros_lib.
BUG=chromium-os:12684
TEST=Ran it a lot ... inspected images after and saw tests pass.
Review URL: http://codereview.chromium.org/6698017
Change-Id: Icd96d1178eeabf45a2d5916fbcab8bf7ffba7e21
Change-Id: I9fed7319609848ba90abfaa147fad85bd4114fdc
BUG=TreeCloser
TEST=Ran it locally in a VM a cpl times.
Review URL: http://codereview.chromium.org/6696002
git config doesn't behave well if there are multiple callers
calling it at the same time. Since this is best effort anyway,
I'm adding an || true so that multithreads calls to this don't
fail.
I removed my previous work around to this since it wasn't generic enough.
Change-Id: I12f2d3faaa745c1ff675a297bb09c567a88aa185
BUG=chromium-os:13070
TEST=Ran it a lot
Review URL: http://codereview.chromium.org/6693001
The use of the mux can cause issues with some EC 8042 controllers and
result in loss of keyboard/trackpad between suspend/resume/reboot cycles.
We will never have more than keyboard+trackpad attached through the 8042
on our devices so using the mux is unnecessary.
BUG=chrome-os-partner:2700
TEST=manual verification that mux is not probed at boot:
Original:
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
New:
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
Change-Id: I942ab86eb71941ab072ad6a17d15b067ca94439d
Review URL: http://codereview.chromium.org/6679031
Change-Id: Ib5617612be38bb6d7dafcb2edab887c998a676ab
BUG=chromium-os:12951
TEST=Ran it with Simple. Saw logs generated (1_update) and in root/dev_server.log. Ran unittests for cros_build_lib.
Review URL: http://codereview.chromium.org/6672007
cros_run_parallel_vm_tests doesn't work unless you pass --use_emerged; there must be some underlying issue with trying to perform multiple run_remote_tests commands at the same time, even on different VMs. So, remove the option and force --use_emerged on the calls to cros_run_vm_test.
BUG=8544
TEST=run two tests in parallel with cros_run_parallel_vm_tests and see that they both complete.
Change-Id: I1152ca3dd7f1de37261da894b9b903c90c2e6524
Review URL: http://codereview.chromium.org/6612058
Not sure how I missed this.
Change-Id: Icd67b6119cbe5ef59bcf2c42784ac8fd011f2ab9
BUG=chromium-os:12953
TEST=Ran it
Review URL: http://codereview.chromium.org/6659009
Enable the ARM kernel signing procedure in the recovery image. Will remove it
when the procedure is stable.
BUG=chromium-os:12352,chromium-os:1305
TEST=run "build_image" and "mod_image_for_recovery.sh
--crosbug12352_arm_kernel_signing" to create a recovery image.
Then use u-boot recovery mode to boot the recovery image. Successfully verify
and boot the kernel.
Change-Id: I1bf911176c6f3adaebf3aa9abc86488a48a60494
Review URL: http://codereview.chromium.org/6635010
Change-Id: If9603879ed4778a2c6bb037ec9ced0eb86482444
BUG=chromium-os:11682
TEST=Ran on tmp dir with failed test. Saw error log get printed out rather than debug
Review URL: http://codereview.chromium.org/6639001
In http://codereview.chromium.org/6567004 in order to help developers stopping
factory UI, we've added an "chvt 2". However changing foreground terminal may
hang when executing "shutdown -r" inside Wipe test.
Removing the "chvt" call solved this issue. The only side effect is that
developers executing "initctl stop factory" may end seeing a black scren - and
they need to hit Ctrl-Alt-F2 to get the console back.
BUG=chrome-os-partner:2631
TEST=build a factory image then verified following steps:
(1) in VT2, do "initctl stop factory, then C-A-F2: screen changed to VT2.
(2) Execute factory tests until Wipe: reboots immediately when X closed
(3) Execute Reboot in HWID test: reboots immediately when 'reboot' is ACTIVE
Change-Id: Ib6f44a6ad07db08862929179d0fe21cbbcc2b22a
Review URL: http://codereview.chromium.org/6621041
This script recently stopped working when we changed the kernel cmdline.
Fix to be more robust by using rootdev instead.
BUG=12780
TEST=Updated my kernel.
Change-Id: I033f670c5db821863441ea1546c382fce3436c01
Review URL: http://codereview.chromium.org/6628027
Sets up dir paths as follows:
test_root/test_name i.e. SimpleUpdate/<num>_stage
For example:
test_root/testNormalUpdateKeepStateful/2_verify/...test_results...
corresponds to the second invocation of verify image. The test
results for this stage are stored here.
This is a predecessor for storing arbitrary logs e.g. update into
this test results root.
Change-Id: I7183420b5dcb0d6971aa508a338c048c3557e359
BUG=chromium-os:12211
TEST=With simple a full vm test suite w/ w/out explicit test root
set.
Review URL: http://codereview.chromium.org/6614029
