Commit Graph

3 Commits

Author SHA1 Message Date
Darin Petkov
597a79dc85 Fail 'build_image test' if a mod-for-test script fails.
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>
2011-11-28 14:10:46 -08:00
Eric Li
df5bf95764 Change mod_for_test_script to make it work with arm os image.
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
2010-03-15 20:35:59 -07:00
ericli@google.com
66c440d687 Add scripts to modify a rootfs.image for testability.
Review URL: http://chromereview.prom.corp.google.com/1177024

git-svn-id: svn://chrome-svn/chromeos/trunk@91 06c00378-0e64-4dae-be16-12b19f9950a1
2009-10-26 21:40:12 +00:00