https://bugs.kde.org/show_bug.cgi?id=511717
--- Comment #22 from Libor Peltan <[email protected]> --- Hi Philippe, thanks much for your extensive answer and for trying to run Knot's tests. The "can't start all servers" message says that the test was not even able to run Knot DNS's binary. Could you please look into the "stdout" and "stderr" files (with oldest unixtime suffix) to search for the reason? The same is also the cause why the test infrastructure launched multiple instances of Knot above each other. Normally, only one instance of the server (and of valgrind) per configuration file is launched. The error what you should see is either "OK" (when the valgrind issue doesn't reproduce) or "Can't get SOA, zone='<something>', server='knot1'" (or knot2, whichever failed). You might need multiple attempts after "OK" for the issue to reproduce. Anyway. The good news is, that the issue reproduces also with --vgdb=full and --tool=none I'm uploading new logs into the Attachments, please see them. -- You are receiving this mail because: You are watching all bug changes.
