The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/7a18e56b2045f57fb5b2f3834ff669f62ea0bfaa

commit 7a18e56b2045f57fb5b2f3834ff669f62ea0bfaa
Author: Aviv Keshet <akeshet@chromium.org>
Date: Tue Feb 28 20:16:20 2017

chromeos_config: temporarily mark lakitu-paladin experimental

BUG= chromium:697166 
TEST=None

Change-Id: I959b8ecd178d1f0444985b3421fe809f1c221a6a
Reviewed-on: https://chromium-review.googlesource.com/448018
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>

[modify] https://crrev.com/7a18e56b2045f57fb5b2f3834ff669f62ea0bfaa/cbuildbot/config_dump.json
[modify] https://crrev.com/7a18e56b2045f57fb5b2f3834ff669f62ea0bfaa/cbuildbot/chromeos_config.py

lakitu-paladin seems to have come back green. I think we can revert the last change now?

https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-paladin/builds/5708

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/6a86b295edaa3c3c835367471a74b2ed2783b6ac

commit 6a86b295edaa3c3c835367471a74b2ed2783b6ac
Author: Daniel Wang <wonderfly@google.com>
Date: Thu Mar 02 23:12:43 2017

Revert "chromeos_config: temporarily mark lakitu-paladin experimental"

This reverts commit 7a18e56b2045f57fb5b2f3834ff669f62ea0bfaa.

Reason for revert: lakitu-paladin has come back green since the DockerHub outage was over.

Original change's description:
> chromeos_config: temporarily mark lakitu-paladin experimental
>
> BUG= chromium:697166 
> TEST=None
>
> Change-Id: I959b8ecd178d1f0444985b3421fe809f1c221a6a
> Reviewed-on: https://chromium-review.googlesource.com/448018
> Reviewed-by: Aviv Keshet <akeshet@chromium.org>
> Reviewed-by: Ben Chan <benchan@chromium.org>
> Tested-by: Aviv Keshet <akeshet@chromium.org>
>

TBR=benchan@chromium.org,akeshet@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.
BUG= chromium:697166 

Change-Id: I6184613522e5a55ae38eabf2408c4cde35e55615
Reviewed-on: https://chromium-review.googlesource.com/448243
Commit-Ready: Daniel Wang <wonderfly@google.com>
Tested-by: Daniel Wang <wonderfly@google.com>
Reviewed-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Amey Deshpande <ameyd@google.com>

[modify] https://crrev.com/6a86b295edaa3c3c835367471a74b2ed2783b6ac/cbuildbot/config_dump.json
[modify] https://crrev.com/6a86b295edaa3c3c835367471a74b2ed2783b6ac/cbuildbot/chromeos_config.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/ba5eb189ef31889451ab883068f3677b8fe406f1

commit ba5eb189ef31889451ab883068f3677b8fe406f1
Author: Xixuan Wu <xixuan@chromium.org>
Date: Fri Mar 03 21:01:51 2017

Revert "Revert "chromeos_config: temporarily mark lakitu-paladin experimental""

https://luci-milo.appspot.com/buildbot/chromeos/lakitu-paladin/5743, lakitu VMTest failed again.

This reverts commit 6a86b295edaa3c3c835367471a74b2ed2783b6ac.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> Revert "chromeos_config: temporarily mark lakitu-paladin experimental"
> 
> This reverts commit 7a18e56b2045f57fb5b2f3834ff669f62ea0bfaa.
> 
> Reason for revert: lakitu-paladin has come back green since the DockerHub outage was over.
> 
> Original change's description:
> > chromeos_config: temporarily mark lakitu-paladin experimental
> >
> > BUG= chromium:697166 
> > TEST=None
> >
> > Change-Id: I959b8ecd178d1f0444985b3421fe809f1c221a6a
> > Reviewed-on: https://chromium-review.googlesource.com/448018
> > Reviewed-by: Aviv Keshet <akeshet@chromium.org>
> > Reviewed-by: Ben Chan <benchan@chromium.org>
> > Tested-by: Aviv Keshet <akeshet@chromium.org>
> >
> 
> TBR=benchan@chromium.org,akeshet@chromium.org
> # Not skipping CQ checks because original CL landed > 1 day ago.
> BUG= chromium:697166 
> 
> Change-Id: I6184613522e5a55ae38eabf2408c4cde35e55615
> Reviewed-on: https://chromium-review.googlesource.com/448243
> Commit-Ready: Daniel Wang <wonderfly@google.com>
> Tested-by: Daniel Wang <wonderfly@google.com>
> Reviewed-by: Ben Chan <benchan@chromium.org>
> Reviewed-by: Amey Deshpande <ameyd@google.com>
> 

TBR=benchan@chromium.org,akeshet@chromium.org,ameyd@google.com,wonderfly@google.com,saied@google.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= chromium:697166 

Change-Id: Ib9e7382749fc9df2fedd96c60e100f4fccb8c84d
Reviewed-on: https://chromium-review.googlesource.com/448943
Reviewed-by: Xixuan Wu <xixuan@chromium.org>
Commit-Queue: Xixuan Wu <xixuan@chromium.org>
Tested-by: Xixuan Wu <xixuan@chromium.org>

[modify] https://crrev.com/ba5eb189ef31889451ab883068f3677b8fe406f1/cbuildbot/config_dump.json
[modify] https://crrev.com/ba5eb189ef31889451ab883068f3677b8fe406f1/cbuildbot/chromeos_config.py

lakitu failure:

https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Flakitu-paladin%2F5743%2F%2B%2Frecipes%2Fsteps%2FGCETest__attempt_1_%2F0%2Fstdout

Traceback (most recent call last):
03/03 18:59:22.532 ERROR|         traceback:0013|   File "/usr/local/autotest/common_lib/log.py", line 25, in decorated_func
03/03 18:59:22.535 ERROR|         traceback:0013|     fn(*args, **dargs)
03/03 18:59:22.537 ERROR|         traceback:0013|   File "/usr/local/autotest/bin/base_sysinfo.py", line 379, in log_before_each_iteration
03/03 18:59:22.540 ERROR|         traceback:0013|     board = utils.get_board_with_frequency_and_memory()
03/03 18:59:22.543 ERROR|         traceback:0013|   File "/usr/local/autotest/bin/site_utils.py", line 845, in get_board_with_frequency_and_memory
03/03 18:59:22.547 ERROR|         traceback:0013|     frequency = int(round(get_cpu_max_frequency() * 1e-8)) * 0.1
03/03 18:59:22.550 ERROR|         traceback:0013|   File "/usr/local/autotest/bin/site_utils.py", line 758, in get_cpu_max_frequency
03/03 18:59:22.553 ERROR|         traceback:0013|     paths = _get_cpufreq_paths('cpuinfo_max_freq')
03/03 18:59:22.556 ERROR|         traceback:0013|   File "/usr/local/autotest/bin/site_utils.py", line 906, in _get_cpufreq_paths
03/03 18:59:22.559 ERROR|         traceback:0013|     paths = utils.run(cmd, verbose=False).stdout.splitlines()
03/03 18:59:22.562 ERROR|         traceback:0013|   File "/usr/local/autotest/common_lib/base_utils.py", line 740, in run
03/03 18:59:22.565 ERROR|         traceback:0013|     "Command returned non-zero exit status")
03/03 18:59:22.569 ERROR|         traceback:0013| CmdError: Command <ls /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq> failed, rc=2, Command returned non-zero exit status
03/03 18:59:22.571 ERROR|         traceback:0013| * Command:
03/03 18:59:22.573 ERROR|         traceback:0013|     ls /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq
03/03 18:59:22.576 ERROR|         traceback:0013| Exit status: 2
03/03 18:59:22.579 ERROR|         traceback:0013| Duration: 0.00153589248657
03/03 18:59:22.581 ERROR|         traceback:0013|
03/03 18:59:22.584 ERROR|         traceback:0013| stderr:
03/03 18:59:22.586 ERROR|         traceback:0013| ls: cannot access /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq: No such file or directory

I feel it's not related to this bug (like a GCE problem). But I'm not sure. Could someone verify it and then I will reopen lakitu-paladin?

Thanks for looking into it Xixuan. We'll look into the test failure, but most likely it was a flake (the subsequent lakitu-paladin run passed). We do plan to improve the robustness of GceTestStage and our tests though.

Assigning to wonderfly@ who has been working on this.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/52d4e4c858cd854a9c1ee2e1dd23c4c7925decc9

commit 52d4e4c858cd854a9c1ee2e1dd23c4c7925decc9
Author: Daniel Wang <wonderfly@google.com>
Date: Wed Mar 08 02:07:31 2017

chromeos_config: temporarily disable run_gce_tests for lakitu-paladin

We want lakitu-paladin to be "important", to avoid surprises like
chromium:699156. On the other hand, we don't want to create too much
noise for the CQ deputies either, so we'll temporarily disable GCE tests
for lakitu-paladin, while we are working to reduce their flakiness.

BUG= chromium:697166 
TEST=run_tests and trybot against lakitu-paladin doesn't run
GCETestStage

Change-Id: I14e04c1b5bf1a99255d27bd4bccd233e0acaec8a
Reviewed-on: https://chromium-review.googlesource.com/450871
Commit-Ready: Daniel Wang <wonderfly@google.com>
Tested-by: Daniel Wang <wonderfly@google.com>
Reviewed-by: Aditya Kali <adityakali@google.com>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Xixuan Wu <xixuan@chromium.org>

[modify] https://crrev.com/52d4e4c858cd854a9c1ee2e1dd23c4c7925decc9/cbuildbot/config_dump.json
[modify] https://crrev.com/52d4e4c858cd854a9c1ee2e1dd23c4c7925decc9/cbuildbot/chromeos_config.py