odd failures from 9.12.2-P2

Discussion:

Dennis Clarke

2018-10-18 23:21:49 UTC

I see these results :

I:System test result summary:
I: 7 FAIL
I: 69 PASS
I: 4 SKIPPED
I: 12 UNTESTED
I:The following system tests failed:
I: autosign
I: catz
I: dnssec
I: filter-aaaa
I: legacy
I: mkeys
I: staticstub

This is on Solaris 10 sparc and using the Oracle Studio 12.6 tools as
well as OpenSSL 1.1.1 which passes all tests.

Is there a way to dig out more information from these failures?

Dennis
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-***@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Evan Hunt

2018-10-19 03:38:30 UTC

Permalink

Post by Dennis Clarke
I: 7 FAIL
I: 69 PASS
I: 4 SKIPPED
I: 12 UNTESTED
I: autosign
I: catz
I: dnssec
I: filter-aaaa
I: legacy
I: mkeys
I: staticstub
This is on Solaris 10 sparc and using the Oracle Studio 12.6 tools as
well as OpenSSL 1.1.1 which passes all tests.
Is there a way to dig out more information from these failures?

Yes, the full output from all of the system tests will be in
bin/tests/system/systests.output, and you can look for messages that
say "I:autosign:failed" (or whatever) to find out which bits didn't
work.

Each of the failing system tests should also have its directory full of
files that were created during the test -- they would have been deleted
if it had passed but should still be there now -- which can also be
used to work out what went wrong.

If you want to just tar up bin/tests/system and send it to me, I'd be
happy to take a look.

--
Evan Hunt -- ***@isc.org
Internet Systems Consortium, Inc.
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-***@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Dennis Clarke

2018-10-19 03:58:56 UTC

Permalink

Post by Evan Hunt

Yes, the full output from all of the system tests will be in
bin/tests/system/systests.output, and you can look for messages that
say "I:autosign:failed" (or whatever) to find out which bits didn't
work.
Each of the failing system tests should also have its directory full of
files that were created during the test -- they would have been deleted
if it had passed but should still be there now -- which can also be
used to work out what went wrong.
If you want to just tar up bin/tests/system and send it to me, I'd be
happy to take a look.

Thank you very much and I appreciate the offer. Really I do.
I'll go digging ... however I jumped onto 9.12.3 while the bits were
still hot from the oven .. so ... only two tests failed :

I:System test result summary:
I: 2 FAIL
I: 74 PASS
I: 4 SKIPPED
I: 12 UNTESTED
I:The following system tests failed:
I: dnssec
I: nsupdate

I will go have a look and not tie up your time. Yet :-\

Dennis Clarke
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-***@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Dennis Clarke

2018-10-19 04:29:00 UTC

Permalink

oh .. also .. I'll look into these and see if I can clean them up :

"zone.c", line 4275: warning: syntax error: empty declaration

"client.c", line 2983: warning: argument #2 is incompatible with prototype:

"zoneconf.c", line 242: warning: argument #2 is incompatible with prototype:

Dennis
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-***@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Mukund Sivaraman

2018-10-19 03:40:42 UTC

Permalink

Each of the above are sub-directories in bin/tests/system, one per
system test. Within these, you'll have sub-directories named "ns<N>"
(where N is a digit). Within these, you'll typically have files with the
name "named.run" which is the debug logging output of a named process
that was run during the system test.

Looking into these log files will reveal why the tests failed (other
than the messages logged by the test script itself). It's not for the
faint-of-heart and you have to be well-versed with BIND to understand
and debug issues if the system tests themselves are failing for anything
but trivial failures.

Mukund
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-***@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users