AutoQA vs Bodhi – round 2

[Kamil Paral]

As you probably noticed not so long ago we announced [1] that AutoQA [2] would be sending comments to Bodhi [3] and inform package maintainers about the results of important test cases (depcheck and ugpradepath). We enabled the functionality and disabled it again very soon due to a number of problems that were discovered. Good news – we’re going for round two!

In the first run we discovered some bugs in our test code, but we also found a number of packages that were incorrectly tagged as pending updates even though they had been in the stable repository for a long time already. The former problem should be solved by AutoQA 0.4.6 [4] (and 0.4.5 [5]) which we are releasing today. The latter problem was fixed on Bodhi side by Luke Macken (huge thanks for quick response). Hopefully now the package maintainers won’t receive any alerts about already pushed package updates, only about the newly proposed ones.

AutoQA Bodhi comments should be re-enabled today. As mentioned before we will quickly disable them if something goes wrong, fix the problem, then re-enable them again. If you don’t receive any AutoQA results for your package, don’t be surprised. However if you receive results but they seem to be wrong, please tell us so that we can investigate: autoqa-devel [6] or #fedora-qa [7]. 

Thanks!


[1] http://kparal.wordpress.com/2011/03/21/autoqa-will-be-providing-comments-for-fedora-updates-really-soon/
[2] https://fedoraproject.org/wiki/AutoQA
[3] https://admin.fedoraproject.org/updates/
[4] https://fedorahosted.org/autoqa/milestone/0.4.6
[5] https://fedorahosted.org/autoqa/milestone/0.4.5
[6] https://fedorahosted.org/mailman/listinfo/autoqa-devel
[7] http://webchat.freenode.net/?channels=fedora-qa