coverity: run tests on smoked rather than master.

In retrospect there isn't much point in defering coverity until the
tree has been through a full test and it just results in potentially
longer gaps between runs with larger numbers of commits included (for
example the run on Sunday was skipped because master hadn't moved
forward since Wednesday).

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>

diff --git a/ap-fetch-version b/ap-fetch-version
index 03ee7545cb62f3dd27b337f22606d2193bb210ec..af2feaee2b3e372a487890e1ac7af1e0b01e2d64 100755 (executable)
--- a/ap-fetch-version
+++ b/ap-fetch-version
@@ -54,7 +54,7 @@ xen-4.*-testing)
                $TREE_XEN staging-$branchcore $LOCALREV_XEN
        ;;
 xen-unstable-coverity)
-       repo_tree_rev_fetch_git xen $TREE_XEN master $LOCALREV_XEN
+       repo_tree_rev_fetch_git xen $TREE_XEN smoked $LOCALREV_XEN
        ;;
 qemu-mainline)
        repo_tree_rev_fetch_git $branch \

diff --git a/ap-fetch-version-old b/ap-fetch-version-old
index 920b1056fa442e21b8e53d002cd40816fadd8424..8efd52358249e19be975f7431cf7198c2e1be3df 100755 (executable)
--- a/ap-fetch-version-old
+++ b/ap-fetch-version-old
@@ -60,7 +60,7 @@ xen-4.*-testing)
                $TREE_XEN stable-$branchcore $LOCALREV_XEN
        ;;
 xen-unstable-coverity)
-       repo_tree_rev_fetch_git xen $TREE_XEN coverity-tested/master $LOCALREV_XEN
+       repo_tree_rev_fetch_git xen $TREE_XEN coverity-tested/smoked $LOCALREV_XEN
        ;;
 qemu-mainline)
         repo_tree_rev_fetch_git $branch \

diff --git a/ap-push b/ap-push
index eeff4a940b02f0ee13e63f3781ed06dcfac6bb92..2ca419fa432a649ce439067017e7e8289258e942 100755 (executable)
--- a/ap-push
+++ b/ap-push
@@ -70,7 +70,7 @@ xen-*-testing)
        ;;
 xen-unstable-coverity)
        cd $repos/xen
-       git push $TREE_XEN $revision:refs/heads/coverity-tested/master
+       git push $TREE_XEN $revision:refs/heads/coverity-tested/smoked
        ;;
 qemu-mainline)
        cd $repos/qemu-mainline