Closed
Bug 97209
Opened 23 years ago
Closed 23 years ago
backward compatibility test failures not all reported
Categories
(NSS :: Test, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
3.4
People
(Reporter: sonja.mirtitsch, Assigned: sonja.mirtitsch)
References
Details
Can neither fix nor test at the moment, but there are a lot of test(failure)s filtered at the moment, which did not pass in 3.2, but our new bc tests are run against 3.2.2, where they should pass
Assignee | ||
Comment 1•23 years ago
|
||
Need to change the way the files are compared, adding at least one TMP file
Severity: normal → major
Priority: -- → P2
Target Milestone: --- → 3.4
Assignee | ||
Updated•23 years ago
|
Assignee | ||
Comment 2•23 years ago
|
||
the straight comparison produces a false alarm from something in output log. need to fix for 3.3.1 release on redhat 7.1, or at least for 3.3.2
Target Milestone: 3.4 → 3.3.2
Assignee | ||
Comment 3•23 years ago
|
||
main issue seems to be the before-context and after-context grep: a/log a b c b/log: xxx yyy zzz grep --before-context=10 xxx */log will produce all lines of a/log a/log: a a/log: b a/log: c b/log: xxx
Assignee | ||
Comment 4•23 years ago
|
||
workaround to reset the before-context-grep and after context grep before the backwardcompatibility tests, fix might be to include empty lines in the QA logs?
Assignee | ||
Comment 5•23 years ago
|
||
Workaround good enough for 3.3.2, changed to 3.4
Severity: major → normal
Target Milestone: 3.3.2 → 3.4
Assignee | ||
Comment 6•23 years ago
|
||
Decided firest part of the fix + workaround for backward compatibility tests is good enough, developers never seem to use this information anyway, failures there are rare enough that I can live with having to scroll through the output.log
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•