From: Petr Vorel <pvorel@suse.cz>
To: Avinesh Kumar <avinesh.kumar@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH] network: Remove outdated DNS stress tests
Date: Mon, 3 Aug 2026 14:27:28 +0200 [thread overview]
Message-ID: <20260803122728.GA242002@pevik> (raw)
In-Reply-To: <20260731200322.161590-1-avinesh.kumar@suse.com>
Hi Avinesh,
> These tests start a local named server and run $NS_TIMES
> (default: 10) dig queries from the remote host, forward and reverse.
> The check is that the first and last query return NOERROR with one
> answer record, and that no dig call in between exited non-zero.
> They are also broken: dns-stress02-rmt.sh passes 'dig -n' for ipv6,
> an option removed from bind long ago. dig prints "dig: -n removed",
> sends no query and exits 0.
> Remove these old broken tests based on legacy shell API.
Thanks, I always wanted to delete them.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Follow-up: 99c0b167d ("network: Remove outdated TCP stress tests")
...
> +++ b/runtest/net_stress.appl
> @@ -1,13 +1,10 @@
> -# Stress test for major application protocol (ssh, dns, http, ftp)
> +# Stress test for major application protocol (ssh, http, ftp)
> ssh4-stress ssh-stress.sh
> ssh6-stress ssh-stress.sh -6
FYI removal of SSH stress tests ...
> -dns4-stress dns-stress.sh
> -dns6-stress dns-stress.sh -6
> -
> http4-stress http-stress.sh
> http6-stress http-stress.sh -6
... and HTTP stress tests is blocked by
https://github.com/linux-test-project/ltp/issues/1207
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-03 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 20:03 [LTP] [RFC PATCH] network: Remove outdated DNS stress tests Avinesh Kumar via ltp
2026-07-31 20:21 ` [LTP] " linuxtestproject.agent
2026-08-03 12:27 ` Petr Vorel [this message]
2026-08-03 12:32 ` [LTP] [RFC PATCH] " Andrea Cervesato via ltp
2026-08-10 12:07 ` Cyril Hrubis
2026-08-11 5:55 ` Petr Vorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260803122728.GA242002@pevik \
--to=pvorel@suse.cz \
--cc=avinesh.kumar@suse.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox