Bug 1296231 - Run upstream tests during build process
Run upstream tests during build process
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: tcpdump (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Martin Sehnoutka
BaseOS QE Security Team
Depends On:
  Show dependency treegraph
Reported: 2016-01-06 11:27 EST by Jaroslav Aster
Modified: 2017-09-06 05:34 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1296230
Last Closed: 2017-09-06 05:34:47 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jaroslav Aster 2016-01-06 11:27:08 EST
+++ This bug was initially created as a clone of Bug #1296230 +++

Description of problem:

The source file of tcpdump contains upstream tests. It would be good to run these tests during build process to avoid potential failures or regressions.

note: Tests were run before, but the run was disabled because some pcap files missed so the run always failed. Check the spec file for more details.
Comment 3 Tomáš Hozza 2017-09-06 05:34:47 EDT
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:


Note You need to log in before you can comment on or make changes to this bug.