Knot Resolver issueshttps://gitlab.nic.cz/knot/knot-resolver/-/issues2024-03-22T13:36:52+01:00https://gitlab.nic.cz/knot/knot-resolver/-/issues/907CI tests for cross-compilation2024-03-22T13:36:52+01:00Oto ŠťávaCI tests for cross-compilationDiscussion from !1503:
- [ ] @ostava started a [discussion](https://gitlab.nic.cz/knot/knot-resolver/-/merge_requests/1503#note_295121): (+1 comment)
> Idea: what if we had a cross-compilation test in the CI? And I mean not necess...Discussion from !1503:
- [ ] @ostava started a [discussion](https://gitlab.nic.cz/knot/knot-resolver/-/merge_requests/1503#note_295121): (+1 comment)
> Idea: what if we had a cross-compilation test in the CI? And I mean not necessarily for Turris, but let's say something like:
>
> * **Job 1:** cross-compile for ARM on x86
> * **Job 2:** run tests on the cross-compiled executable from **Job 1** on ARM
>
> Since we do have arm64 runners available, it *could* be easy enough to do?
Not urgent, just an idea for improvement.https://gitlab.nic.cz/knot/knot-resolver/-/issues/871datamodel: better testing of Lua configuration rendering2023-09-28T04:38:51+02:00Aleš Mrázekdatamodel: better testing of Lua configuration renderingLua configuration rendering is not sufficiently tested and it is possible that other bugs will appear.
For example bug in !1461.Lua configuration rendering is not sufficiently tested and it is possible that other bugs will appear.
For example bug in !1461.6.1.0Aleš MrázekAleš Mrázekhttps://gitlab.nic.cz/knot/knot-resolver/-/issues/744tests/packaging: failing tests2022-06-01T14:06:50+02:00Oto Šťávatests/packaging: failing testsI'm opening this issue so that we are tracking these test fails somewhere, but I'm not sure what we can do about them.
* `centos_7`
* outdated `luarocks` (is `2.x` required `3.x`) - cannot install `process`. I've tried to resolve th...I'm opening this issue so that we are tracking these test fails somewhere, but I'm not sure what we can do about them.
* `centos_7`
* outdated `luarocks` (is `2.x` required `3.x`) - cannot install `process`. I've tried to resolve this by explicitly installing older `process`, that does not require the new `luarocks`, but it attempts to install the new version anyway
* `centos_8`
* appstream fails to prepare internal mirrorlist
* no such command `config-manager`
* `fedora_31`
* outdated `knot` - is `3.0.1`, required `3.0.2`
* `leap_15.2`
* package conflicts
Related MR: !1304 (adds better logging for failing commands)https://gitlab.nic.cz/knot/knot-resolver/-/issues/635ci: add respdiff tests for XDP2020-10-30T15:21:26+01:00Tomas Krizekci: add respdiff tests for XDPXDP should be tested on real interfaces, which requires some changes to respdiff configuration (using real interface instead of loopback, root privileges, ...). This might be easier to achieve once we simplify our testing infrastructure....XDP should be tested on real interfaces, which requires some changes to respdiff configuration (using real interface instead of loopback, root privileges, ...). This might be easier to achieve once we simplify our testing infrastructure. (https://gitlab.nic.cz/knot/knot-resolver-ansible/-/issues/3)https://gitlab.nic.cz/knot/knot-resolver/-/issues/606incorporate DNS Shotgun into kresd CI2020-10-30T11:55:49+01:00Petr Špačekincorporate DNS Shotgun into kresd CIThe following discussion from !1054 should be addressed:
- [ ] @pspacek started a [discussion](https://gitlab.nic.cz/knot/knot-resolver/-/merge_requests/1054#note_169587): (+1 comment)
> @tkrizek Do you see a way to add this scena...The following discussion from !1054 should be addressed:
- [ ] @pspacek started a [discussion](https://gitlab.nic.cz/knot/knot-resolver/-/merge_requests/1054#note_169587): (+1 comment)
> @tkrizek Do you see a way to add this scenation into pytests/connection tests?https://gitlab.nic.cz/knot/knot-resolver/-/issues/578test aggressive cache on NSEC3PARAM rotation2020-08-20T10:05:40+02:00Vladimír Čunátvladimir.cunat@nic.cztest aggressive cache on NSEC3PARAM rotationI don't think we have any tests on that in particular, though the code's been deployed for a long time. Still, most of possible failures I can imagine should only lead to insufficient caching.
Hints around how the implementation works:...I don't think we have any tests on that in particular, though the code's been deployed for a long time. Still, most of possible failures I can imagine should only lead to insufficient caching.
Hints around how the implementation works:
- NSEC3PARAM is the [data collected](https://tools.ietf.org/html/rfc5155#section-4.2) but it's taken from NSEC3 records directly.
- For this purpose, using NSEC is like one more possible NSEC3PARAM configuration.
- Reading from cache is designed to consider the last two NSEC3PARAMs that's been written for that zone.
- Code reference: identifiers containing `nsec_p`.https://gitlab.nic.cz/knot/knot-resolver/-/issues/569clarify respdiff job names in CI2020-10-19T11:16:35+02:00Petr Špačekclarify respdiff job names in CIMostly note for myself:
especially forwarding scenarios have confusing names
Find better naming structure and fix it.
Rename will break a lot of stuff so schedule this when we have time for it.Mostly note for myself:
especially forwarding scenarios have confusing names
Find better naming structure and fix it.
Rename will break a lot of stuff so schedule this when we have time for it.https://gitlab.nic.cz/knot/knot-resolver/-/issues/534CI: test server selection algorithm2019-12-18T19:41:28+01:00Petr ŠpačekCI: test server selection algorithmImplement https://gitlab.labs.nic.cz/knot/maze/ into Knot Resolver's CI.
Ideas:
- Gitlab shell executor in a VM with sudo access (yuck!)
- shell executor to a VM with a systemd build which contains https://github.com/systemd/systemd/pul...Implement https://gitlab.labs.nic.cz/knot/maze/ into Knot Resolver's CI.
Ideas:
- Gitlab shell executor in a VM with sudo access (yuck!)
- shell executor to a VM with a systemd build which contains https://github.com/systemd/systemd/pull/138232020 Q1Štěpán BalážikŠtěpán Balážikhttps://gitlab.nic.cz/knot/knot-resolver/-/issues/360make sure contrib/ does not get out of sync with libknot upstream2018-05-24T19:08:06+02:00Petr Špačekmake sure contrib/ does not get out of sync with libknot upstreamThis needs some clever idea how to compare against correct branch etc. See !588 for an example.This needs some clever idea how to compare against correct branch etc. See !588 for an example.https://gitlab.nic.cz/knot/knot-resolver/-/issues/252Test DNS64 module with weird answers2017-12-17T01:10:17+01:00Petr ŠpačekTest DNS64 module with weird answersPresentation [DNS64 at scale – Turning off IPv4](https://indico.dns-oarc.net/event/27/session/2/contribution/0) contains on slide 14 queries which return intentionally weird answers. We should test our DNS64 module that it reacts reasona...Presentation [DNS64 at scale – Turning off IPv4](https://indico.dns-oarc.net/event/27/session/2/contribution/0) contains on slide 14 queries which return intentionally weird answers. We should test our DNS64 module that it reacts reasonably.
If there is something which is not RFC-compliant, let's fix it in the DNS64 module. If there is something worth fixing for non-compliant cases, it should probably be in workarounds module.
Please talk to me before introducing workarounds for non-compliant cases.
Also, this might require some new Deckard tests.https://gitlab.nic.cz/knot/knot-resolver/-/issues/187test etcd module2017-10-09T17:00:34+02:00Petr Špačektest etcd moduleAn open question is how to mock etcd.An open question is how to mock etcd.https://gitlab.nic.cz/knot/knot-resolver/-/issues/185test graphite module2019-12-18T18:39:02+01:00Petr Špačektest graphite moduleThis might be lower priority than other tests.This might be lower priority than other tests.https://gitlab.nic.cz/knot/knot-resolver/-/issues/182fuzz & fix configuration interface to avoid segfaults2020-10-09T19:18:24+02:00Petr Špačekfuzz & fix configuration interface to avoid segfaultsOften a typo in config file can lead to segfault. We might try to write a fuzzer for config file and see what happens.Often a typo in config file can lead to segfault. We might try to write a fuzzer for config file and see what happens.