| Summary: | messages about skipped tests when running upstream test suite | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Hubert Kario <hkario> |
| Component: | nss | Assignee: | Daiki Ueno <dueno> |
| Status: | CLOSED ERRATA | QA Contact: | Hubert Kario <hkario> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | kengert, szidek |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | nss-3.34.0-0.1.beta1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-10 09:23:57 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: | |
|
Description
Hubert Kario
2016-12-06 14:43:35 UTC
Sounds like a request to fix NSS tests as part of the RPM packing. Does this also happen when the test is executed outside the scope of an RPM build? If yes, we need an upstream bug. Could this potentially be a deliberate decision of the upstream test suite, e.g. related to its multiple cycles, and when some tests aren't appropriate? Does this still happen with the newer 3.28.x package? Is this a regression (from packages older than 3.21.x)? (In reply to Kai Engert (:kaie) from comment #1) > Sounds like a request to fix NSS tests as part of the RPM packing. well, it is a RHEL bug... :) > Does this also happen when the test is executed outside the scope of an RPM > build? If yes, we need an upstream bug. haven't tested > Could this potentially be a deliberate decision of the upstream test suite, > e.g. related to its multiple cycles, and when some tests aren't appropriate? maybe, but the formatting of the errors doesn't fell like this to me > Does this still happen with the newer 3.28.x package? not tested > Is this a regression (from packages older than 3.21.x)? I would have to double check, but I did in the past go through full test script results and didn't notice them before, so yes, I'd bet on "it's a regression" I suggest that as a first step for this bug, it should be evaluated, how much our logs differ from the upstream logs. Does upstream skip the same messages? Then this needs to be fixed upstream first. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0679 |