| Age | Commit message (Collapse) | Author |
|---|
|
Update ChromeOS Object bisector to work with new compiler wrapper. This
new compiler wrapper means we can now do incremental switches and triage
builds that skip compiler calls.
TEST=Run full bisection
CQ-DEPEND=CL:368231
Change-Id: If34877519ad6dfe3189a5e934e174fd13dae5c89
Reviewed-on: https://chrome-internal-review.googlesource.com/274236
Commit-Ready: Caroline Tice <cmtice@google.com>
Tested-by: Caroline Tice <cmtice@google.com>
Reviewed-by: Caroline Tice <cmtice@google.com>
|
|
Refactor warning! Move install.sh, boot_test.sh, and interactive_test.sh
into common folder so they can be shared by both package and object
bisectors. To allow this sharing, sysroot_wrapper now has a setup script
similar to cros_pkg. All scripts now source common/common.sh.
TEST=Run unit tests, run system tests, run couple iterations of install
script for both bisectors.
Change-Id: I9e164b4e6b842ff321c2400201e6ac0984f99088
Reviewed-on: https://chrome-internal-review.googlesource.com/268027
Commit-Ready: Cassidy Burden <cburden@google.com>
Tested-by: Cassidy Burden <cburden@google.com>
Reviewed-by: Caroline Tice <cmtice@google.com>
|
|
Add new testing script to sysroot_wrapper bisector and make all shell
scripts for sysroot_wrapper bisector executable.
TEST=Run new test on chromeos-chrome
Change-Id: I312e50108e36341517ed1f8ea6b8d415e4184c2e
Reviewed-on: https://chrome-internal-review.googlesource.com/265975
Commit-Ready: Cassidy Burden <cburden@google.com>
Tested-by: Cassidy Burden <cburden@google.com>
Reviewed-by: Caroline Tice <cmtice@google.com>
|
|
Scripts to be used by the binary searching tool to interact with
the bisecting functionality in the sysroot_wrapper.
BUG=None
TEST=Tested on 3 different occasions while triaging problems
in flash, kernel and glibc.
Change-Id: Icf55f60b0cb160ae453c9384ca77da70710c3f48
Reviewed-on: https://chrome-internal-review.googlesource.com/188665
Reviewed-by: Han Shen <shenhan@google.com>
Commit-Queue: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
|
