I still would like to take rats_install test. I am also OK to take the rats_sanity test. And I am afraid the mediakit_sanity test will miss the target before the release. I have hit some problems. such as the output orders are different when run sanity.py separately and wrap it with mediakit_sanity.
Hongqing
----- Original Message -----
From: "Martin Krizek" mkrizek@redhat.com To: "AutoQA development" autoqa-devel@lists.fedorahosted.org Sent: Tuesday, February 28, 2012 1:47:11 AM Subject: Re: require maintainer defined for each test & clean up current tests
----- Original Message -----
From: "Kamil Paral" kparal@redhat.com To: "AutoQA development" autoqa-devel@lists.fedorahosted.org Sent: Monday, February 27, 2012 3:11:21 PM Subject: require maintainer defined for each test & clean up current tests
- repoclosure, conflicts - this lists potential dependency problems
and file conflicts for the whole repository. Until now no one cared. With resultsdb frontend we can finally have a page that lists all the results day by day. It means someone can go through the results occasionally and file some bugs. The question is: who? It's nice to have some results, but if we just *hope* someone will do something about it, that seems too uncertain for me. They are also somewhat obsoleted by depcheck. I'm sitting on the fence here.
I've never look at 'conflicts' test but if there isn't anyone who is knowledgeable regarding this test, I am happy to take it. It seems quite useful to me. And since it's already written it would be pity just to throw it away. Of course, the question on how to spread the results among the package maintainers remains...
Martin _______________________________________________ autoqa-devel mailing list autoqa-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/autoqa-devel