All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] ipneigh01: Replace TCONF error message with TINFO
Date: Mon, 7 May 2018 15:31:36 +0300	[thread overview]
Message-ID: <1c3154be-b015-9ae9-7b00-ea0c45c0368f@oracle.com> (raw)
In-Reply-To: <c6c5f26d-8fea-7419-3b0c-e4977afbf296@suse.de>

On 05/07/2018 02:13 PM, Anton Smorodskyi wrote:
> Hi Alexey
> 
> This is my first attempt to contribute to LTP project. Disadvantage of this is the fact that I can ask some obvious for you question ( hope you will forgive me that) , but advantage that I have a fresh look so I can point out to something that is wrong but you just get used too.
> 
> First of all let's clarify something not related to this PR directly :
> 
> 

Hi Anton,

>>> And why it is more appropriate? TCONF is not an error message.
> In LTP documentation TCONF defined as - "The test case was not appropriate for the current hardware or software configuration". So I would not call it error too but I would say that it is some flavor of "SKIPPED" state.
> Where you want to say "this test case can't run currently so I can't say if it is passed or failed"

No, I don't.


> 
> Second thing which needs to be taken in consideration  I clarified with Petr Vorel in conversation outside this ML - test counter changed only on TPASS or TFAIL. This lead us to really confusing log output :
> 
>  1.
>     ipneigh01 1 TINFO: initialize 'lhost' 'ltp_ns_veth2' interface
>  2.
>     ipneigh01 1 TINFO: set local addr 10.0.0.2/24
>  3.
>     ipneigh01 1 TINFO: set local addr fd00:1:1:1::2/64
>  4.
>     ipneigh01 1 TINFO: initialize 'rhost' 'ltp_ns_veth1' interface
>  5.
>     ipneigh01 1 TINFO: set remote addr 10.0.0.1/24
>  6.
>     ipneigh01 1 TINFO: set remote addr fd00:1:1:1::1/64
>  7.
>     ipneigh01 1 TINFO: Network config (local -- remote):
>  8.
>     ipneigh01 1 TINFO: ltp_ns_veth2 -- ltp_ns_veth1
>  9.
>     ipneigh01 1 TINFO: 10.0.0.2/24 -- 10.0.0.1/24
> 10.
>     ipneigh01 1 TINFO: fd00:1:1:1::2/64 -- fd00:1:1:1::1/64
> 11.
>     ipneigh01 1 TCONF: 'arp cmd doesn't support IPv6, skipping test-case
> 12.
>     ipneigh01 1 TINFO: Stress auto-creation of NDISC cache entry
> 13.
>     ipneigh01 1 TINFO: by pinging 'fd00:1:1:1::1' and deleting entry again
> 14.
>     ipneigh01 1 TINFO: with 'ip neigh del fd00:1:1:1::1 dev ltp_ns_veth2'
> 15.
>     ipneigh01 1 TPASS: verified adding/removing of NDISC cache entry
> 
> Please correct me if I missing something but I read this like "ok we can't run this test case because arp cmd doesn't support IPv6 , ah but wait test case is passed ".
>> After all discussions around that patch and all info which I gain I can agree that changing TCONF with TINFO was bad idea , but if we will just "fix" issue by changing TST_TOTAL value to 1 ( if I correctly understand your suggestion )
> this will not remove this confusion.	

I've not suggested to change TST_TOTAL.

> 
> Only valid fix which I see is change behavior of LTP to change test case counter after TCONF which makes total sense for me , but most probably I missing something and you had some reasons to not changing counter on TCONF messages. Can you please elaborate them ?

Yes, this is a flaw in the test.sh library.

And it would be better to convert the test to use tst_test.sh.

      parent reply	other threads:[~2018-05-07 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 11:36 [LTP] [PATCH 1/1] ipneigh01: Replace TCONF error message with TINFO Anton Smorodskyi
2018-05-04 14:18 ` Alexey Kodanev
2018-05-04 14:41   ` Petr Vorel
2018-05-07 11:13     ` Anton Smorodskyi
2018-05-07 12:13       ` Petr Vorel
2018-05-07 12:31       ` Alexey Kodanev [this message]

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=1c3154be-b015-9ae9-7b00-ea0c45c0368f@oracle.com \
    --to=alexey.kodanev@oracle.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 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.