NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

bin/52207: rump/rumpkern/t_kern fails

>Number:         52207
>Category:       bin
>Synopsis:       Test rump/rumpkern/t_kern fails
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 01 22:35:00 +0000 2017
>Originator:     Paul Goyette
>Release:        NetBSD 7.99.66
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:          |
| (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee dot com   |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd dot org |
System: NetBSD 7.99.66 NetBSD 7.99.66 (SPEEDY 2017-03-24 21:50:36 UTC) #0: Fri Mar 24 22:50:09 UTC 2017 amd64
Architecture: x86_64
Machine: amd64
The string comparisons that check for exptected output are incorrect.  For
example, the first testcase expects the string

	"mutex error: lockdebug_free: is locked or in use"

Yet the actual string returned is

	"mutex error: mutex_destroy,139: lockdebug_free: is locked or in use"

The inclusion of the function name and line number cause the comparison
to fail, and thus a successful test completion is reported as a failure.

Note that this test program is normally atf_skip()ed, unless the rump
kernel was built with LOCKDEBUG.  Thus this error is not seen on the
rel-eng automated test-beds.
Perhaps do a regex match on the returned text, rather than a simple
string compare?

Or, check for the common prefix "mutex error:", skip the function and line
number, and then compare the rest of the returned text to the argument?



Home | Main Index | Thread Index | Old Index