Petr Menšík 35a69710cc Do not expect fail in cpu test default configuration ... Previous CPU test relied on either missing default named.conf or the missing permissions to write into its default directory. In short that default configuration would be unusable with current user. It would hang indefinitely at cpu test if the named user could write into directory specified in default configuration. Change it instead to explicitly try non-existent configuration file. It will still fail immediately, but will not rely on running user or presence of file at default configuration file path. (cherry picked from commit 8e789ea62f)		2025-06-25 11:36:39 +00:00
..
ns1	Follow the number of CPU set by taskset/cpuset	2024-09-03 14:54:40 +02:00
prereq.sh	Follow the number of CPU set by taskset/cpuset	2024-09-03 14:54:40 +02:00
setup.sh	Remove invocations and mentions of clean.sh	2024-11-11 15:04:52 +01:00
tests.sh	Do not expect fail in cpu test default configuration	2025-06-25 11:36:39 +00:00
tests_sh_cpu.py	Replace clean.sh files with extra_artifacts mark	2024-11-11 15:04:52 +01:00