Kea issueshttps://gitlab.isc.org/isc-projects/kea/-/issues2019-05-15T17:40:08Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/597TeeTest.calculateTimers unittest failing2019-05-15T17:40:08ZWlodzimierz WencelTeeTest.calculateTimers unittest failingsince [#360,!305] was merged there is one unit test that is keep failing.
https://jenkins.isc.org/job/kea-master/348/testReport/junit/(root)/TeeTest/Multi_node_testing_loop___fedora27_32___results___calculateTimers/
it's failing just ...since [#360,!305] was merged there is one unit test that is keep failing.
https://jenkins.isc.org/job/kea-master/348/testReport/junit/(root)/TeeTest/Multi_node_testing_loop___fedora27_32___results___calculateTimers/
it's failing just on fedora 27 32 bit. fedora27-32-2Kea1.6Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/kea/-/issues/526Improve MySQL unit test time by implementing a wipe-data only mechanism2019-04-10T11:35:46ZThomas MarkwalderImprove MySQL unit test time by implementing a wipe-data only mechanismMySQL and MariaDB variants can be extremely slow doing schema updates. The current mechanism creates and destroys the schema between each MySQL unit test. With dramatic increase in schema size and the number of unit tests, test executio...MySQL and MariaDB variants can be extremely slow doing schema updates. The current mechanism creates and destroys the schema between each MySQL unit test. With dramatic increase in schema size and the number of unit tests, test execution has become untenable.
Rather than creating and destroying the schema each time, it should be sufficient for each test to determine if it has the correct schema version and then simply wipe the transient data from the database upon entry and exit.
If the schema version is incorrect (or non existent), the schema should be destroyed and recreated. In theory this should happen infrequently, once a environment's unit test schema
is correct.Kea1.6Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/kea/-/issues/431Write a script that cleans up config backend DB2019-04-10T11:35:45ZTomek MrugalskiWrite a script that cleans up config backend DB@marcin and @tomek discussed a concept of wiping database. This may address several issues:
- system tests need to discard all data from a DB after a CB test.
- after schema was extended, every unit-test creates and then tears down the ...@marcin and @tomek discussed a concept of wiping database. This may address several issues:
- system tests need to discard all data from a DB after a CB test.
- after schema was extended, every unit-test creates and then tears down the schema. With many (around 40) tables, this is very slow process. We should have an option (possibly even enabled by default) to wipe data from the tables rather then tear them down and recreate every time. (TRUNCATE TABLE is supposedly faster than DELETE FROM, but has some constraints and can't be used everywhere).Kea1.6https://gitlab.isc.org/isc-projects/kea/-/issues/357unit tests create too long socket paths that are not allowed by unix systems2019-03-07T11:25:26ZMichal Nowikowskiunit tests create too long socket paths that are not allowed by unix systemsUnit tests should create safe socket path e.g. in /tmp folder.
There is KEA_SOCKET_TEST_DIR but this is not obvious for new comers or sporadic users.Unit tests should create safe socket path e.g. in /tmp folder.
There is KEA_SOCKET_TEST_DIR but this is not obvious for new comers or sporadic users.Kea1.6Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/kea/-/issues/214add colors to services states in keactrl2019-05-14T15:18:10ZMichal Nowikowskiadd colors to services states in keactrlKea1.6Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/kea/-/issues/82Improve Kea test capabilities2019-01-25T19:18:24ZGhost UserImprove Kea test capabilitiesKea accepts the "-p" switch to change the port on which it listens. However, there appears to be no way to alter the port to which it sends replies. Similarly perfdhcp accepts the "-L" switch to alter the local port (the port on which ...Kea accepts the "-p" switch to change the port on which it listens. However, there appears to be no way to alter the port to which it sends replies. Similarly perfdhcp accepts the "-L" switch to alter the local port (the port on which it listens for responses? - this is not clear), but there appears to be no way to alter the port to which it sends packets.
Although full testing on the privileged ports using multiple systems would still need to be carried out before release, it would simplify a lot of development testing if Kea and perfdhcp could (with suitable switch settings) communicate via unprivileged ports on the loopback interface.Kea1.6Francis DupontFrancis Dupont