graphics_GLMark2: add back a glmark2 dep to install test on device
Oops. It turns out the recommended practice for autotests is to have
autotest install the test binaries via autotest deps, rather than baking
them into the test image.
Since we are using the dep to install the glmark2 executable, we might as
well just call it glmark2 always, even if it is really glmark2-es2.
This simplifies the autotest a bit.
Note: By default glmark2 looks for its resources at a path hardcoded at
build time. When built from the app-benchmarks/glmark2 ebuild, this path
will be "/usr/share/glmark2/". However, autotest can't copy the resources
to this location on the test machine; the share contents are copied to
autotest/deps/glmark2/data instead. Thus, we invoke glmark2 with its
"--data-dir" option.
Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
BUG=chromium:330529
TEST=emerge-${B} --unmerge glmark2 autotest-deps-glmark2 autotest-tests
TEST=TESTS=graphics_GLMark2 emerge-autotest-tests
TEST=run_remote_tests.sh graphics_GLMark2
CQ-DEPEND=CL:184283
Change-Id: I26142c7c5e585dcc8b9a1e25fa3c6ef71d33f6a0
Reviewed-on: https://chromium-review.googlesource.com/184316
Reviewed-by: Ilja Friedel <ihf@chromium.org>
Reviewed-by: Dominik Behr <dbehr@chromium.org>
Tested-by: Daniel Kurtz <djkurtz@chromium.org>
Commit-Queue: Doug Anderson <dianders@chromium.org>
5 files changed