Nicki Křížek 4c487c811d Use pytest.mark.flaky as the flaky marker ... It's possible to use pytest.mark.flaky, which achieves the exact same thing as our custom-defined isctest.mark.flaky -- attempts to rerun the test on failure, but only is flaky package is available.		2025-07-07 13:29:15 +02:00
..
ans2	Avoid global namespace pollution	2025-04-11 09:14:57 -05:00
ans3	Avoid global namespace pollution	2025-04-11 09:14:57 -05:00
ans4	Avoid global namespace pollution	2025-04-11 09:14:57 -05:00
ns1	Replace the trivial setup.sh system test files	2025-04-15 14:11:16 +02:00
ns5	Replace the trivial setup.sh system test files	2025-04-15 14:11:16 +02:00
ns6	Replace the trivial setup.sh system test files	2025-04-15 14:11:16 +02:00
ns7	Replace the trivial setup.sh system test files	2025-04-15 14:11:16 +02:00
prereq.sh	Reformat shell scripts with shfmt	2023-10-26 10:23:50 +02:00
qmin_ans.py	Use isctest.asyncserver in the "qmin" test	2025-03-18 06:19:01 +01:00
tests.sh	Don't leak the original QTYPE to parent zone	2025-03-14 01:01:26 +00:00
tests_sh_qmin.py	Use pytest.mark.flaky as the flaky marker	2025-07-07 13:29:15 +02:00