RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

See https://fedoraproject.org/wiki/Packaging:Guidelines#Test_Suites


There appears to be two make targets to test the package: make check and make test
but they are not executed in %check.


Version-Release number of selected component (if applicable):
pykickstart-1.99.43-1.el7.src.rpm

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.