we don't want any possibility for firmware to be changed in factory setup
BUG=none
TEST=build_image; image_to_usb --factory
Change-Id: Ibef767ea621193afb7fbca5ea96120a506891dcb
R=nsanders@chromium.org
Review URL: http://codereview.chromium.org/6764010
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
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
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
Developers may want to run their own factory test UI after finishing the
Google official one, so the "factory" test should be stoppable.
BUG=chrome-os-partner:2456
TEST=build a factory image, install and start factory testing UI,
then switch to VT2, login and type: "initctl stop factory"
the screen should switch to a virtual terminal (VT2) without
hanging / reboot.
Change-Id: I6a9d1c951d48d448f5c83c5f645ea531e8fd1499
Review URL: http://codereview.chromium.org/6567004
The factory tests should not use default results folder, otherwise a developer
running autotests by command line would corrupt the whole factory test
framework.
Since tools/autotest cannot support additional parameters and our state (to
continue) is clear, the command is also changed to directly invoke bin/autotest.
BUG=chrome-os-partner:2378
TEST=manually patched into a factory test device and verified factory
UI works at new boot and a reboot.
Change-Id: I9f6ef31114bdda740319072c6f9ac624f6850b95
Review URL: http://codereview.chromium.org/6529046
I'm changing the boot-complete init script to start on
login-prompt-visible instead of login-prompt-ready in
http://codereview.chromium.org/5868004/.
This also adds a missing description and fixes an outdated
email address.
BUG=chromium-os:10349
TEST=ran mod_image_for_test.sh with --factory and with --factory_install and checked that resulting image contained boot-complete.conf change
Review URL: http://codereview.chromium.org/5975002
Change-Id: I709bc2b4eaaccd222b31388633522c32514206ac
- Conditionally patch chrontel.conf
- Add a patch for nvrm to start on factory, so that X can start.
BUG=crosbug.com/p/1721
TEST=Built and run factory image for tegra2_seaboard
Change-Id: Ied87b6d959f940ef8e99e124ab419fdeea48aa26
Review URL: http://codereview.chromium.org/5126005
This caused a build break after http://codereview.chromium.org/3995007 was
committed, since we try to patch a now-nonexistent file.
BUG=None
TEST=Adhoc
./mod_image_for_test.sh --factory_install doesn't hang
Change-Id: Iac299c850765eedfcefcffb80c385b0e8c0fa277
Signed-off-by: Elly Jones <ellyjones@chromium.org>
Signed-off-by: Kliegs <kliegs@chromium.org>
Review URL: http://codereview.chromium.org/3973004
A file name changed which breaks the factory test phase on the builders.
This change was LGTM'd but not submitted.
Patch from Tom Wai-Hong Tam <waihong@chromium.org>.
Change-Id: I961515ba4667891d82833035f2d312a653f746fd
* Leave ui.conf there, not run by default.
* dump autotest log into /dev/tty1
* Don't let tty1 eat keayboard events.
Review URL: http://codereview.chromium.org/1742018
