public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 4/4] network: Fix tst_brk TFAIL
Date: Wed, 24 Jan 2024 14:48:38 +0100	[thread overview]
Message-ID: <20240124134838.GA295776@pevik> (raw)
In-Reply-To: <9f884555-dbd3-46f8-8eaf-000815bf404c@suse.cz>

Hi Martin,

> Hi,
> two comments below.

...
> > +++ b/testcases/network/virt/virt_lib.sh
> > @@ -174,8 +174,10 @@ virt_multiple_add_test()
> >   	tst_res TINFO "add $NS_TIMES $virt_type, then delete"
> >   	for i in $(seq $start_id $max); do
> > -		virt_add ltp_v$i id $i $opt || \
> > -			tst_brk TFAIL "failed to create 'ltp_v0 $opt'"
> > +		if ! virt_add ltp_v$i id $i $opt; then
> > +			tst_res TFAIL "failed to create 'ltp_v0 $opt'"
> > +			return

> This is a library function so tst_brk TBROK is probably the correct fix
> here. Also, the message should say ltp_v$i instead of ltp_v0, but that's for
> a separate patch.

Thanks! tst_brk TBROK makes sense here.

ltp_v$i fixed in separate commit with your credit (merged now).

> > +		fi
> >   		ROD_SILENT "ip link set ltp_v$i up"
> >   	done
> > @@ -196,8 +198,10 @@ virt_add_delete_test()
> >   	tst_res TINFO "add/del $virt_type $NS_TIMES times"
> >   	for i in $(seq 0 $max); do
> > -		virt_add ltp_v0 $opt || \
> > -			tst_brk TFAIL "failed to create 'ltp_v0 $opt'"
> > +		if ! virt_add ltp_v0 $opt; then
> > +			tst_res TFAIL "failed to create 'ltp_v0 $opt'"
> > +			return

> Same here.

Yes (tst_brk TBROK).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-01-24 13:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 16:26 [LTP] [PATCH 0/4] shell: fix regression since 1878502f6 Petr Vorel
2024-01-23 16:26 ` [LTP] [PATCH 1/4] tst_test.sh: Improve info on wrong tst_brk param Petr Vorel
2024-01-23 16:26 ` [LTP] [PATCH 2/4] commands: Fix tst_brk TFAIL Petr Vorel
2024-01-23 16:26 ` [LTP] [PATCH 3/4] kernel: " Petr Vorel
2024-01-24 10:57   ` Cyril Hrubis
2024-01-24 12:02     ` Petr Vorel
2024-01-24 12:19       ` Cyril Hrubis
2024-01-24 17:18         ` Petr Vorel
2024-01-23 16:26 ` [LTP] [PATCH 4/4] network: " Petr Vorel
2024-01-24 12:34   ` Martin Doucha
2024-01-24 13:48     ` Petr Vorel [this message]
2024-01-24  9:31 ` [LTP] [PATCH 0/4] shell: fix regression since 1878502f6 Li Wang

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=20240124134838.GA295776@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    /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