>>>>> "RB" == Randy Barlow <bowlofeggs@xxxxxxxxxxxxxxxxx> writes: RB> https://taskotron.fedoraproject.org/resultsdb/results?testcases=dist.python-versions.python_usage This one seems on-point. rpm 4.14.1-9.fc28 fails: https://taskotron.fedoraproject.org/resultsdb/results/21327930 Is it possible to filter only failures out of the results list? RB> So we could look through these to find packages that fail. Of RB> course, a downside to this approach is that there will only be data RB> for packages that have been built since these tests existed, so RB> unmaintained packages might not appear in these results even though RB> they could have problems. That's pretty much the same for most things in this domain. Any change we make to any build-time configuration isn't going to have any effect until packages are actually built. Still, at least personally I would much rather have something fail when I do a mock build to tell me that something deep within the build process is calling /usr/bin/python. Waiting until after the slowest koji builder has managed to churn through a package to find out that you missed a python execution somewhere is not nearly as useful. Obviously there are some tasks which simply require higher level testing, and having those results presented in a searchable manner is great, but that's no replacement for failing early when that is possible. - J< _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/F5LKBKQ5R6XQQQJLT4WFQVPZZLP5XMRK/
