public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v3 2/2] net/route: Add netlink based route change gw/dest tests
Date: Fri, 10 Apr 2020 17:27:09 +0200	[thread overview]
Message-ID: <20200410152709.GA2245028@x230> (raw)
In-Reply-To: <bd634f12-b4f2-18ad-c2f3-ab5e42a0c973@oracle.com>

Hi Alexey,

> Then, for now we can pass arbitrary port, no need for tst_get_unused_port(),
> e.g. 65535.
Right, it really does not matter to check that port.


> >>> +	EXPECT_PASS route-change-netlink -c $NS_TIMES -d $(tst_iface) $ip_flag -p $port $ROUTE_CHANGE_NETLINK_PARAMS

> >> EXPECT_PASS doesn't handle TCONF when libmnl-devel is missing.

> > Thanks, I'll fix it.

> > tst_test.c:865: CONF: libmnl library and headers are required
> > route-change-netlink-gw 1 TFAIL: route-change-netlink -c 10 -d ltp_ns_veth2 -p 40645 -g 10.23.1.7^10.23.1.6^10.23.1.5^10.23.1.4^10.23.1.3^ -l 10.23.1.1 -r 10.23.0.1 failed unexpectedly

> > I propose to handle this in EXPECT_PASS() (send a separate RFC patch for it).

> Not sure if it would work for non-ltp binaries...
True. Do you think there would be more usage for something like
EXPECT_PASS_LTP(), where I'd handle 32 as TCONF, 3 as TFAIL, 4 as TWARN?
I can handle it just in the test.

BTW there is this error handling already in tst_netload() for netstress.c, so
there could be function which returns $res according to exit code and
EXPECT_PASS_LTP() which uses it.

Kind regards,
Petr

      reply	other threads:[~2020-04-10 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 16:54 [LTP] [RFC PATCH v3 0/2] Route tests using netlink API (dst,gw) Petr Vorel
2020-04-03 16:54 ` [LTP] [RFC PATCH v3 1/2] net: Move setup_addrinfo() into tst_net.h Petr Vorel
2020-04-09 14:44   ` Alexey Kodanev
2020-04-03 16:54 ` [LTP] [RFC PATCH v3 2/2] net/route: Add netlink based route change gw/dest tests Petr Vorel
2020-04-03 16:59   ` Petr Vorel
2020-04-03 17:02   ` Petr Vorel
2020-04-09 15:25   ` Alexey Kodanev
2020-04-09 18:37     ` Petr Vorel
2020-04-10 13:01       ` Alexey Kodanev
2020-04-10 15:27         ` Petr Vorel [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=20200410152709.GA2245028@x230 \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox