Adam Williamson 1fdf7cd567 Handle update build not having any packages for target arch ... openQA sometimes winds up testing an update that doesn't have any packages for x86_64 (or aarch64). The most common case is s390utils, which is on the critpath but only has packages for s390x. I would ideally like to skip scheduling entirely if the update has no packages for the arch we're scheduling on, but sadly that involves using the Koji API which is XML-RPC and I don't really want to deal with that again. This deals with it at the test level instead, by checking the error message if `koji download-build` fails and carrying on if it's the "no packages for this arch" error. That means if the update has no packages at all for our arch we're not really testing anything, but that's better than a bunch of false failures, I guess. Signed-off-by: Adam Williamson <awilliam@redhat.com>		2020-10-07 09:49:03 -07:00
..
anaconda.pm	Finish the post review changes.	2020-05-28 13:32:42 -07:00
anacondatest.pm	Add perl syntax check test, add it to CI	2020-02-13 15:28:09 -08:00
cockpit.pm	Update cockpit needles and select_cockpit_update for 220	2020-05-30 10:27:20 -07:00
fedoradistribution.pm	Add perl syntax check test, add it to CI	2020-02-13 15:28:09 -08:00
freeipa.pm	Great Needle Cleanup 2020	2020-03-20 14:02:10 -07:00
installedtest.pm	post_fail_hook: upload PostgreSQL init log if it exists	2020-08-25 16:18:32 -07:00
packagetest.pm	Replace remaining wait_idles with sleeps	2020-01-02 17:44:45 -08:00
tapnet.pm	Use nmcli for static network stuff, not ifcfg files	2020-09-02 14:49:29 -07:00
utils.pm	Handle update build not having any packages for target arch	2020-10-07 09:49:03 -07:00