Rev Chrome whenever the 9999 ebuild changes.
Rev Chrome whenever the 9999 ebuild changes.

When the Chrome PFQ was first deployed, there were no prebuilts for Chrome,
so updating Chrome had a 1 hour cost per developer. As a result, we only
revved Chrome when the Chrome version changed and not when the 9999 ebuild
changed.

Now that we have prebuilts for Chrome, it is fine to update Chrome more often
and allow 9999 ebuild changes to be tested / deployed sooner.

BUG=chromium-os:26995
TEST=Trybot runs with and without sample 9999 ebuild change.

Change-Id: I718a75a87a2ac8f6a8c0d3730515357c5fcaf49b
Reviewed-on: https://gerrit.chromium.org/gerrit/37322
Reviewed-by: Chris Sosa <959d3d631fb6f17f1b07f751372041a1edb210d1@chromium.org>
Commit-Ready: David James <f231dc574bbeb62604660cbc162d1b8642a0a3af@chromium.org>
Tested-by: David James <f231dc574bbeb62604660cbc162d1b8642a0a3af@chromium.org>

zhang0137/chromite,zhang0137/chromite,coreos/chromite,chadversary/chromiumos.chromite,bpsinc-native/src_third_party_chromite,bpsinc-native/src_third_party_chromite,chadversary/chromiumos.chromite,zhang0137/chromite,bpsinc-native/src_third_party_chromite,coreos/chromite,coreos/chromite