https://bugs.kde.org/show_bug.cgi?id=511717
--- Comment #27 from Libor Peltan <[email protected]> --- `Maybe the problem is linked with the speed at which the knot server starts ?` Yes, that is possible. My experience is that running a complex application under (deliberately) heavy test load requires quite a CPU power :) FYI I just tried to reproduce the issue on a clear Ubuntu 25.10 installation in VirtualBox. It did reproduce. I only called a handful of commands: ``` sudo apt install git vim libtool autoconf automake make pkg-config liburcu-dev libgnutls28-dev libedit-dev liblmdb-dev python3-full pipx valgrind git clone https://gitlab.nic.cz/knot/knot-dns.git cd knot-dns/ autoreconf -if ./configure --enable-static CFLAGS="-gdwarf-4 -O0" make cd tests-extra/ mkdir ~/pyvenv python3 -m venv ~/pyvenv/ source ~/pyvenv/bin/activate pip3 install -r requirements.txt ./runtests.py ctl/concurrent ``` Anyway, I have compiled valgrind from current git sources with that improvement, and after the issue reproduced, I'm attaching newest logs as always. I hope it helps this time :) -- You are receiving this mail because: You are watching all bug changes.
