| Summary: | pykickstart test suite not executed in %check | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Alexander Todorov <atodorov> |
| Component: | pykickstart | Assignee: | Chris Lumens <clumens> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Release Test Team <release-test-team> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | atodorov |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pykickstart-1.99.43.6-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-13 11:18:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 1024724 | ||
|
Description
Alexander Todorov
2013-10-31 09:45:23 UTC
They are run before the source package is built, as well as upon every commit here locally. What purpose does yet another layer of running the same thing provide? I mean, I certainly can add it. It's not hard. I'm just wondering why it needs to get run in another place. Hi Chris, the purpose is to be able to collect the test results and measure test coverage more precisely. QE has no way of getting that info if devel is running the test suite locally. Otherwise it's a good thing you have this running. I've added "make test", but "make check" requires pylint and I don't think we want to add that in to the build process. In version pykickstart-1.99.43.8-1.el7.src.rpm spec file contains: %check make test Moving to verified. This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |