Fix bug where the Unified CQ was revving the wrong MV repo.
Fix bug where the Unified CQ was revving the wrong MV repo.

I missed this call location to add test=True for the unified
logic so the unified master was colliding with the normal
paladin builder.

BUG=chromium-os:30136
TEST=Pylint + unittests

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

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