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
The default DB is an all-pass DB. If no DB found, the hardware_Components test
falls back to the all-pass one and skip the real check. In order to prevent
skipping the check, remove the default DB in the boards already have DB
directories.
TEST=run "image_to_usb.sh --factory" and check the default DB removed
BUG=chrome-os-partner:1737
Change-Id: Ia25f2551a5eba3a95fe736e86bfe52c340f329a8
Review URL: http://codereview.chromium.org/5339011
- 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
Major changes are:
- prefix functions in cros_image_common with 'image' to avoid naming conflicts
- use awk to replace grep+sed+cut
- use case to handle board name list
- factory_setup.sh should return error if applying patch failed
- refine for shell script coding style guide:
* replace `` with $()
* quote variables
* replace "! -z" by "-n"
* no space between redirection symbol (>) and target name (eg, >>filename)
* 1> should be simply >
* no trailing \ for && and ||
BUG=chrome-os-partner:1583
TEST=manually verified:
./image_to_usb.sh --factory # calls mod_image_for_test --factory, and works fine
./make_factory_package.sh --factory PATH_TO_IMAGE --release PATH_TO_IMAGE ...
# factory payloads were created successfully
Change-Id: I6bb10bdfb12cbdb14e9816b3ad72dfe4b7b0472f
Review URL: http://codereview.chromium.org/5168001
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
We use the filename format gbb_${BOARD}_${HWID} for GBB blob files and
place them in the same directory of site_tests/factory_WriteGBB, but in
private git.
Actually, these files will be automatically put in the factory image.
This change is to remove those not belonging to the same board.
Also do some fixes and rename QualDbs stuffs.
TEST=run image_to_usb.sh and check the gbb files.
BUG=chrome-os-partner:789
Change-Id: I5913a14eb3ceef5abfdf1a87156faa6bb7dbd561
Review URL: http://codereview.chromium.org/3111014
All Qual DBs may be existed in the same directory of hardware_Components (overlaid internal git). So, if QUALDB is not specified, first check the existence of DBs matched the board name. Then remove other DBs not belonging to the board.
TEST=build_packages, build_image, image_to_usb
Review URL: http://codereview.chromium.org/3032036
The DBs are named in the format of qualified_components_${BOARD}_${HWQUALID}.
If only one hwqual id for the board, named in qualified_components_${BOARD}.
Review URL: http://codereview.chromium.org/3038026
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
Dropping caches (writing back all dirty pages to disk and clearing all the caches) is not necessary for factory tests. It can reduce the latency significantly. The scale is about 27s -> 3s, for running 2 empty tests.
Review URL: http://codereview.chromium.org/1780011
Add feature to mod_image_for_test to patch rootfs.
Change initctl path to get network but no chrome.
./image_to_usb.sh --install_mfg --install_autotest --test_image
which calls ./mod_image_for_test.sh --manuf
Review URL: http://codereview.chromium.org/1542011
