make_factory_toolkit: add factory-mini.par into toolkit
Some programs (e.g. gooftool and hwid) were designed highly coupled with
Chrome OS and would be more efficient to run locally in comparison to
interaction using remote DUT API, so we decide to keep these programs as
"executed locally" on DUT.
The 'factory-mini.par' provides a simple way to execute such programs by
allowing test program to directly push the par file into remote DUT for
invocation, with only the requirement that DUT enviornment should
already have Python (which is not a problem for Chrome OS test images).
To unify the building process of a par files, we want to keep creating
the par files only one time in build time, and put a copy into factory
toolkit so every test stations can easily find and push the latest par
files.
BUG=None
TEST=`make_factory_toolkit.sh` and install factory toolkit, check if
factory-mini.par is installed.
Change-Id: Ia7a54b1f3650343e6f7b9fa1e2c3bbff46bb2d70
Reviewed-on: https://chromium-review.googlesource.com/330035
Commit-Ready: Wei-Han Chen <stimim@chromium.org>
Tested-by: Wei-Han Chen <stimim@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
1 file changed
