After talking with Adam about the depcheck error reported last week, it seemed like a good idea to start on some basic metrics to get an idea of how many false positives and false negatives we have in our results.
I've written up some basic code that gets a list of updates from the stable request messages in datagrepper over a period of time and uses that list to gather information about bodhi updates. At the moment, the code works well enough to be used for lists of updates to examine but there are still corner cases which aren't well handled (specifically, updates without 32 bit builds) and there's no differentiation between depcheck runs on updates-testing and updates. If anyone is interested, I put the code up on bitbucket: https://bitbucket.org/fedoraqa/taskmetrics Tim
signature.asc
Description: PGP signature
_______________________________________________ qa-devel mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/qa-devel
