From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] runtest/smoketest: Remove intermittent failed test case route4-change-dst
Date: Thu, 9 Sep 2021 12:21:30 +0200 [thread overview]
Message-ID: <YTngKohBcpQK7l5r@pevik> (raw)
In-Reply-To: <20210906083444.82394-1-naresh.kamboju@linaro.org>
Hi Naresh,
> The test case route4-change-dst fails intermittently creating
> the problem for smoketest results verdict. route4-change-dst
> is a stress test should not be a part of smoketest. because of
> these issues removing route4-change-dst from the smoketest.
Could you please be more specific about the failure?
I'm not against adding ping tests into smoketest runtest file,
although just on might be enough. ping02.sh is the fastest from all 3 tests,
maybe add it. Also -6 for IPv6 would be good (to detect problems with IPv6 setup).
But route-change-dst.sh is quick (actually 2 times faster than ping01) that it's
not really a stress test in the default configuration, thus I'd prefer to keep it.
Kind regards,
Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/2] runtest/smoketest: Remove intermittent failed test case route4-change-dst
Date: Thu, 9 Sep 2021 12:21:30 +0200 [thread overview]
Message-ID: <YTngKohBcpQK7l5r@pevik> (raw)
Message-ID: <20210909102130.aoFpL7kxzBBpkTfPmcEJRjh5N9XnD0c8aVl4PD3dKoQ@z> (raw)
In-Reply-To: <20210906083444.82394-1-naresh.kamboju@linaro.org>
Hi Naresh,
> The test case route4-change-dst fails intermittently creating
> the problem for smoketest results verdict. route4-change-dst
> is a stress test should not be a part of smoketest. because of
> these issues removing route4-change-dst from the smoketest.
Could you please be more specific about the failure?
I'm not against adding ping tests into smoketest runtest file,
although just on might be enough. ping02.sh is the fastest from all 3 tests,
maybe add it. Also -6 for IPv6 would be good (to detect problems with IPv6 setup).
But route-change-dst.sh is quick (actually 2 times faster than ping01) that it's
not really a stress test in the default configuration, thus I'd prefer to keep it.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-09-09 10:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 8:34 [LTP] [PATCH 1/2] runtest/smoketest: Remove intermittent failed test case route4-change-dst Naresh Kamboju
2021-09-06 8:34 ` Naresh Kamboju
2021-09-06 8:34 ` [LTP] [PATCH 2/2] runtest/smoketest: Adding ping01 and ping02 test cases Naresh Kamboju
2021-09-06 8:34 ` Naresh Kamboju
2021-09-09 10:21 ` Petr Vorel [this message]
2021-09-09 10:21 ` [LTP] [PATCH 1/2] runtest/smoketest: Remove intermittent failed test case route4-change-dst Petr Vorel
2021-09-10 10:56 ` Naresh Kamboju
2021-09-10 10:56 ` Naresh Kamboju
-- strict thread matches above, loose matches on Subject: below --
2021-09-14 12:24 Naresh Kamboju
2021-09-14 12:24 ` Naresh Kamboju
2021-09-14 12:50 ` Petr Vorel
2021-09-14 12:50 ` Petr Vorel
2021-09-14 13:07 ` Naresh Kamboju
2021-09-14 13:07 ` Naresh Kamboju
2021-09-14 14:48 ` Alexey Kodanev
2021-09-14 14:48 ` Alexey Kodanev
2021-09-14 15:52 ` Petr Vorel
2021-09-14 15:52 ` Petr Vorel
2021-09-06 8:26 Naresh Kamboju
2021-09-06 8:26 ` Naresh Kamboju
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=YTngKohBcpQK7l5r@pevik \
--to=pvorel@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.