test parameters were adjusted accordingly.
there are some non trivial adjustments needed for the 'correct' test
cases for the original loadzone:
- completing the origin for some RDATA paramaeters (NS, SOA) does not
work yet until we complete the RDATA support. At the moment
I made them FQDNs with comments
- a few TXT data were actually incorrect in the original tests, which
caused a seeming regression. I fixed the test data.
- there was one real bug in the $INCLUDE + origin support. I'll go
fix it; right now it fails
The 'error' test cases for the original loadzone also fail, but overall
the intended behavior looked preserved. Fixing the tests to make it pass
seems to be quite difficult (because log output are different, and
the new loadzone ng is more verbose), so I plan to simply remove these
tests.
To verify and update the b10-cmdctl certificate, using a few hardcoded certificate options (cn=localhost, o=BIND10, country=US).
The tool can also be used to update the existing certificate if it has expired (it is only valid for 1 year)
Conflicts:
doc/devel/mainpage.dox
src/lib/dhcp/Makefile.am
src/lib/dhcp/lease_mgr.cc
src/lib/dhcp/lease_mgr.h
src/lib/dhcp/tests/Makefile.am
src/lib/dhcp/tests/lease_mgr_unittest.cc
A number of other files were modified to resolve incompatibilities
in the way lease managers were created, and to promote the dummy
"memfile" lease manager to a fully-fledged lease manager with
unit tests.
this works around a bit awkward installation setup where there's a link
from "python3" to "python3.x" but not from "python3-config" to the
corresponding "python3.x-config". That happens for recent versions of
Homebrew.
by specifying -Qunused-arguments. Also, as a cleanup for better organization
I moved compiler specific settings to earlier part of configure.ac, where
this workaround was added.
This reverts commit daf81c8846.
I believe the sense of the change is correct, but it has effects on
other OSes, so it's probably better to use clang specific workaround
(will commit it later).
Valgrind complains (probably rightfully so) that memory is leaking in death-tests. This has been reported upstream, but is not addressed yet, and may not be in the near future, if at all (one response was don't use EXPECT_DEATH).
So I added a checker function, *if* valgrind headers are available, that returns true if the tests are run under valgrind. Death tests are now ignored if so.
Note that we should be very careful about using this; and only use it for things we are sure valgrind can't help, since it is possible to do things differently when using valgrind, which kind of defeats its purpose
this works around a bit awkward installation setup where there's a link
from "python3" to "python3.x" but not from "python3-config" to the
corresponding "python3.x-config". That happens for recent versions of
Homebrew.
