Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
(In reply to Ademar Reis from comment #1)
> Can't we use a blacklist instead of a whitelist? The reason is that it would
> be good to enable any new tests if a backport includes them.
After discussing this f2f, I've learned that many of the tests are flaky (not stable enough) and odds are some of the new tests will also be flaky. So adding them automatically might cause destabilization of future builds, even if they pass at first.
Also discussed this with Yash, who raised the point that once we make the change to close this BZ, fine-tunning the list will require yet another BZ with an exception flag.
So my suggestion is to introduce the change to run the tests as part of the build process, but don't break the build if a test fail, at least not for now. This can be accomplished by adding the command with a "||:" at the end ("OR nop" in bash). This way we can monitor the official build logs to see if any other tests are failing before we commit to the change.