- poe check: check for difference in JSON schema
- scripts/meson/make-doc.sh: do not create JSON schema

- Do `go mod tidy` before running the test, even in CI
- Add `go.sum` to `.gitignore`
- Compatibility with Go 1.15 (Debian 11)

Aleš Mrázek authored 1 year ago and Oto Šťáva committed 1 year ago

This separates the documentation into a *blue* user documentation and a
*red* developer documentation, resolving problems where similar sections
collided in search queries, leading users to the advanced Lua config
documentation instead of the preferred declarative config one.

It also visually separates the two parts, so that users who do not wish
to meddle in Lua immediately see that they're somewhere wrong just by
seeing the red colour.

It's never gone beyond experiment/alpha and now we have kresctl
which should be much better.  Keeping installed bin/kresc could
confuse users.

Oto Šťáva authored 2 years ago and Vladimír Čunát committed 2 years ago

Added the option to run `kresd` inside `pytests` under `valgrind` and
`rr`, which can help with debugging. Also added a clarifying note that I
personally would have liked to have while exploring this.

They need one go package which I can't find even in Debian,
so it probably can't work without network access.
The new dnstap in extra_tests runs if dnstap is built and go is found.
It also tries to keep the source tree clean.

Now both query and reply messages are tested.

In CI (after caching go deps in image) this tests only takes slightly
more time than the longest config.* tests, so that seems OK.
Even so, it's not added into the valgrind variant, as compilation
of the test still isn't split away from the run itself.

Petr Špaček authored 4 years ago and Tomas Krizek committed 4 years ago

New map() creates control/ sockets in current working directory so it
pollutes worktree when developers run it in worktree.

I've also added files with ephemeral certificates and pytests test report
which were missing as well.

Simon South authored 4 years ago and Tomas Krizek committed 4 years ago

Check for makeinfo during configuration and if found, generate and
install documentation in Info format.

- we have ./systemd/*.d dirs
- with meson we don't do in-tree builds, so *.d files shouldn't appear

For better OBS workflow, it's best if archives are
treated as untracked files.

Marek Vavruša authored 7 years ago and Tomas Krizek committed 6 years ago

The package_version() function returns current build information.
Removed the version module instead of fixing, as it's being obsoleted.

Petr Špaček authored 6 years ago and Vladimír Čunát committed 6 years ago

Temporary directory generated by code coverage measurement.

Our Makefile required >= 2.6.4 for some time already.
It's pretty straightforward, except for zonefile.lua.in -> zonefile.lua

Let's not mix daemon and client files as client might grow to multiple
files in future. This will also help with upcomming changes to packaging
scripts.

Marek Vavruša authored 7 years ago and Petr Špaček committed 7 years ago

I moved the test files to module directories because it allows
vendoring of whole modules including tests etc.

The test environment provides convenience functions and produces
test output in TAP format. Ideally all tests should use a common
format, so that CI can parse it provide better test output on PRs.
It seems like Gitlab CI doesn't support anything yet, but there
are two sort-of standards supported in CI tools - TAP and JUnit.
I chose TAP because it's easier to read for humans, cmocka supports it,
and it should be easier to adapt Deckard. There are also tools to
convert TAP into JUnit XML file.

Also added more tests for global functions and variables, and the
test tool now also tracks coverage (if `luacov` is installed).