This test is failing on the R65 branch consistently, does this test have a server side dependency that broke? 

Or did we actually merge something bad to 65?

Adding some folks whom have touched this test in the past and may know how serious this is.

We need to clear this as a bug on 65 to push the beta today.

It's blocking the CQ too: https://luci-milo.appspot.com/buildbot/chromeos/quawks-paladin/2432

I think the test should be disabled.

Let's disable it first to unblock others.  The "fix" should be easy by replacing the target app, which seems to be gone from Play.

I've run the test locally, and found the following quirk:

- it searches for a package by package name (rs.pedjaapps.Linpack)
- it installs the app whose info card matches the app name ('Linpack')
- later (either at the end of a run, or at the start of a future run) it tries to uninstall by package name (again, rs.pedjapps.Linkpack) so the search will [hopefully, see below] yield a package that is not installed.

The implicit assumption is that the search result yields a package with the same name. In my case, the package installed has package name 'org.skynetsoftware.linpack' so future runs will show "Uninstall" / "Open" UI in play store, so the test can't find the "Install" button (and fail)

I have no clue as to why this *recently* broke, <speculation>perhaps the package used to use the rs.pedjapps.Linpack package name.

(Disabling while this gets sorted out SGTM)

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/c2665a1d18bbeae996e8de68a8b1084184574571

commit c2665a1d18bbeae996e8de68a8b1084184574571
Author: Victor Hsieh <victorhsieh@chromium.org>
Date: Thu Mar 15 17:44:35 2018

Next step: fix the test and re-enable it.

When you remove a test from a blocking bvt suite please move it to bvt-perbuild instead. Otherwise you lose coverage and don't see when to move it back.

Sure, will do it next time.  Though in this case, we'll have to fix the test first, and I'll put them back to bvt-perbuild once it's ready.

Sure, it is just a little less work and smoother to send it right to bvt-perbuild.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/3c9ea292855b176d7b0246b3cab606501f54823c

commit 3c9ea292855b176d7b0246b3cab606501f54823c
Author: Victor Hsieh <victorhsieh@chromium.org>
Date: Thu Mar 15 19:33:31 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/c2e34336cf3c5207e311df48bc6338705e4be279

commit c2e34336cf3c5207e311df48bc6338705e4be279
Author: Victor Hsieh <victorhsieh@chromium.org>
Date: Thu Mar 15 19:33:34 2018

 Issue 822151  has been merged into this issue.

NOTE: Test is (was?) also failing on reef-chrome-pfq, cyan-chrome-pfq, veyron_minnie-chrome-pfq, veyron_minnie-tot-chrome-pfq-informational.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/33c7c46a8087473d65135fb2414c37b5af1d5056

commit 33c7c46a8087473d65135fb2414c37b5af1d5056
Author: Victor Hsieh <victorhsieh@chromium.org>
Date: Tue Mar 20 02:21:44 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/00f0b25fd2c23f531f169e6e872c29bfeb2e9515

commit 00f0b25fd2c23f531f169e6e872c29bfeb2e9515
Author: Victor Hsieh <victorhsieh@chromium.org>
Date: Thu Mar 22 06:23:40 2018