Bug 230503 – NSS needs to provide a test package

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 230503 - NSS needs to provide a test package

Summary:	NSS needs to provide a test package

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	nss (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Kai Engert (:kaie) (inactive account)
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-02-28 21:10 EST by Bob Relyea
Modified:	2008-02-15 11:43 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-02-15 11:43:24 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Bob Relyea 2007-02-28 21:10:11 EST

Description of problem:

Upstream NSS includes in it's tar ball a test script which can verify and NSS
installation. We should make that test script, which the necessary binaries
which aren't already in an NSS package, in it's own package that can be
installed and ran.

Comment 1 Kai Engert (:kaie) (inactive account) 2007-04-17 20:04:42 EDT

Chandra, do you have experience with running the NSS test programs?

Bob R: Is your proposal to run "all.sh" ?

How should this work in detail?

I just tried to run all.sh on my system, I started with
  HOST=localhost DOMSUF=localdomain ./all.sh

and the test seems to be in a kind of endless loop where a TCP test with tstclnt
repeatedly fails.

Should this be a purely optional manual task that someone can run and look at
the test output?

Or, does the script return a single exit code that indicates "all tests succeeded"?

Comment 2 Bob Relyea 2007-05-25 18:46:41 EDT

Your endless loop thing should be identified. I run all.sh on my machines all
the time to verify my fixes.

Unfortunately all.sh itself does not return a rollup success code, but there are
scripts which can determine if all.sh had any failure or not. The tools is
definately meant to be run automatically as well as manually (tinderbox
automatically runs all.sh, for instance, after every build, all.sh failures turn
tinderbox orange rather than red (build failures)).

Comment 3 Kai Engert (:kaie) (inactive account) 2008-02-15 11:43:24 EST

The original approach seemed hard, this is why I had not worked on this bug yet.

However, we did come up with a better idea!
Let's run the test suite as part of the rpm build process.
A successful run of the test suite on the build test is a necessary precondition
to get a rpm package!

This should avoid the need for having the test suite available for installation.

This has been fixed in Rawhide.
Test suite is currently enabled for i386 and x86_64, but temporarily disabled
for ppc and ppc64 because of an upstream failure.

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