repoinfo.conf update should be enough, which I did. But the control
file for rats_sanity is broken, I'm working on a fix.
I intend to have it scheduled only against Branched, not Rawhide.
Since we've started branching Rawhide, we don't concentrate on
Rawhide itself so much, and it's not as critical as before. Also it
would consume machine and maintenance resources I would rather spend
elsewhere. So I think our tests should target Branched first, and
ignore Rawhide for now. Feel free to object.
I have disabled rats_install on production and staging server for the moment. The patch is
here:
diff --git a/tests/rats_sanity/control.autoqa b/tests/rats_sanity/control.autoqa
index 6c99181..a6a8e10 100644
--- a/tests/rats_sanity/control.autoqa
+++ b/tests/rats_sanity/control.autoqa
@@ -1,13 +1,16 @@
# vim: set syntax=python
# Notice: Most recent documentation is available at doc/control.autoqa.template.
-# we want to run rats_sanity just for post-repo-update
+import autoqa.repoinfo
+
+# we want to run rats_sanity just for post-repo-update
if event in ['post-repo-update']:
execute = True
-# Only advertise rats_sanity for branched* and rawhide* tests
-if autoqa_args.has_key('reponame'):
- name = autoqa_args['reponame'].lower()
- if not (name.startswith('rawhide') or name.startswith('branched')):
+ # only run rats_sanity for Branched repo (i.e. composes enabled)
+ if autoqa_args.has_key('name'):
+ repo = autoqa.repoinfo.repoinfo.getrepo(autoqa_args['name'])
+ if not repo['composes']:
+ execute = False
+ else:
execute = False
-
I'll commit tomorrow if there are no concerns.