Hide Forgot
Description of problem: Currently if rpm-test-trigger fails to download an RPM from brew/koji it'll continue the test run, instead it should at this point instead. As the tests can't be expected to succeed without all the RPMs, as well as pick up errors in the non-existent RPMs Actual results: Continues on with the test run even though not all RPMs might have been downloaded. Expected results: That an Error is reported back as an infrastructure error. Additional info:
This is already handled correctly... bug 1383152 fixed the case where Koji returns 404 for a package, and commit 0260b0d4bc0cca079fbf1a04692925290e0a5a6a fixed the case where Koji returns None because it doesn't know about the rpm.