Curious I know we discussed enabling this via control file but would it make more sense to enable it based simply on presence of arc container?

That way once automated runs start working we'd have direct comparisons for cheets vs non-cheets without having to create additional control files.

BTW, Ravi's initial CL is here:https://chromium-review.googlesource.com/#/c/352310

Wasn't the point of this just so we can get runs w/ the container up but on the standard PLT in order to better understand the power delta? In the future, cheets and non-cheets will be the same image, so we need the control files to either disable or enable ARC++. In other words, the container will be present on all minnie images, so we won't be able to differentiate based on whether or not it's there.

That's my current understanding at least

@#c2, sgtm ... Ravi's initial CL proposes control file solution so we should be all set.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Activating. Please assign to the right owner and the appropriate priority.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/b02675147f22255c68769a8226908491a216546d

commit b02675147f22255c68769a8226908491a216546d
Author: Todd Broch <tbroch@google.com>
Date: Wed Nov 15 02:43:56 2017

power_LoadTest: add arc enablement for devices which have it.

BUG= chromium:619735 
TEST=power_LoadTest.fast on eve

Details:
IP=123.456.7.8
test_that $IP power_LoadTest.fast
ssh root@$IP "android-sh -c 'logcat'"

Change-Id: I8e9032dff4c6a0a02355b99685fcf7bb79b7eb41
Reviewed-on: https://chromium-review.googlesource.com/742044
Commit-Ready: Todd Broch <tbroch@chromium.org>
Tested-by: Todd Broch <tbroch@chromium.org>
Reviewed-by: Ravi Chandra Sadineni <ravisadineni@chromium.org>

[modify] https://crrev.com/b02675147f22255c68769a8226908491a216546d/client/site_tests/power_LoadTest/power_LoadTest.py