| Summary: | rpm-test-trigger still runs tests and reports results even if the product is not applicable | ||
|---|---|---|---|
| Product: | [Community] rpm-test-trigger | Reporter: | Dan Callaghan <dcallagh> |
| Component: | general | Assignee: | beaker-dev-list |
| Status: | MODIFIED --- | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unreleased | CC: | jorris |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Dan Callaghan
2016-12-07 05:11:09 UTC
A related problem: we are checking the release (and its applicability) for every advisory in the dependency chain. We don't need to do that -- what matters is whether the advisory we are actually testing is applicable or not. Seems like the fix is to shuffle things around so that the get_release_for_advisory() test is done before calling get_builds_for_errata(). |