On Tue, Sep 20, 2022 at 03:23:51PM +0200, Gert Doering wrote:
> If t_client.sh is run interactively, more verbose output is useful
> to quickly see what it is doing. If run from a CI environment, going
> through lots of output for successful tests just to find the one that
> failed is non-useful.
On Mon, Sep 26, 2022 at 10:11:58AM +0200, Gert Doering wrote:
> In addition to global FPING_EXTRA_ARGS now also evaluate
> FPING_ARGGS_.
>
> This can be used, for example, for a test instance for "will ToS-tagged
> packets be sent properly?" by setting FPING_ARGS_2="-O 0x10".
>
Trivial change.
Hi,
On 27/09/2022 11:43, Frank Lichtenheld wrote:
On Tue, Sep 20, 2022 at 03:23:51PM +0200, Gert Doering wrote:
If t_client.sh is run interactively, more verbose output is useful
to quickly see what it is doing. If run from a CI environment, going
through lots of output for successful tests
Thanks for the review & testing ;-)
Patch has been applied to the master branch.
commit 398f73094a692ba46be7e3205b65d915d2593a64
Author: Gert Doering
Date: Tue Sep 20 15:23:51 2022 +0200
introduce V= level to manage t_client.sh output verbosity
Signed-off-by: Gert Doering
Thanks for the review.
Patch has been applied to the master branch.
commit 27229d174d4dec2cbfcf05865d49ef48442c2ff3
Author: Gert Doering
Date: Mon Sep 26 10:11:58 2022 +0200
t_client: add per-instance arguments to fping
Signed-off-by: Gert Doering
Acked-by: Frank Lichtenheld
