A CQ run may submit changes partially even when the build as a while failed if test failures are not related to those changes. However, A CQ run publishes a binhost change ONLY IF the build as a whole succeeds.

Due to this behavior, while CQ is red, contents of binhost gets more and more stale, which forces more packages to be built locally in build_packages.

Note that this is problematic in combination with following other issues:

1. These days CQ is not very stable and it's not surprising to see it's red for several days.

2. Some packages are uprev'ed even if no change directly touches them. For example chromeos-base/modem-utilities was uprev'ed 288 times in last 5 months, while platform2/modem-utilities was changed only 2 times this year.