From: Cyril Hrubis <chrubis@suse.cz>
To: kernel test robot <oliver.sang@intel.com>
Cc: "Patrick Rohr" <prohr@google.com>,
lkp@intel.com, "Maciej Żenczykowski" <maze@google.com>,
netdev@vger.kernel.org, "Jason Wang" <jasowang@redhat.com>,
lkp@lists.01.org, "David S . Miller" <davem@davemloft.net>,
ltp@lists.linux.it, "Lorenzo Colitti" <lorenzo@google.com>
Subject: Re: [LTP] [tun] a4d8f18ebc: ltp.ioctl03.fail
Date: Wed, 21 Sep 2022 09:48:33 +0200 [thread overview]
Message-ID: <YyrB0fSRu7PvNvLi@yuki> (raw)
In-Reply-To: <202209211425.14116dd2-oliver.sang@intel.com>
Hi!
> tag=ioctl03 stime=1663640405
> cmdline="ioctl03"
> contacts=""
> analysis=exit
> <<<test_output>>>
> tst_test.c:1526: TINFO: Timeout per run is 0h 02m 30s
> ioctl03.c:76: TINFO: Available features are: 0x7533
> ioctl03.c:80: TPASS: TUN 0x1
> ioctl03.c:80: TPASS: TAP 0x2
> ioctl03.c:80: TPASS: NO_PI 0x1000
> ioctl03.c:80: TPASS: ONE_QUEUE 0x2000
> ioctl03.c:80: TPASS: VNET_HDR 0x4000
> ioctl03.c:80: TPASS: MULTI_QUEUE 0x100
> ioctl03.c:80: TPASS: IFF_NAPI 0x10
> ioctl03.c:80: TPASS: IFF_NAPI_FRAGS 0x20
> ioctl03.c:85: TFAIL: (UNKNOWN 0x400)
Obviously the test fails since new flag has been advertised. The test
will have to be updated once/if this commit hits mainline.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2022-09-21 7:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 23:45 [PATCH] tun: support not enabling carrier in TUNSETIFF Patrick Rohr
2022-09-16 23:54 ` Maciej Żenczykowski
2022-09-19 6:52 ` Jason Wang
2022-09-19 17:18 ` Stephen Hemminger
2022-09-20 0:01 ` Maciej Żenczykowski
2022-09-20 1:44 ` Jason Wang
2022-09-20 15:36 ` Stephen Hemminger
2022-09-20 19:48 ` [PATCH v2] " Patrick Rohr
2022-09-20 21:47 ` Maciej Żenczykowski
2022-09-21 2:53 ` Jason Wang
2022-09-21 6:35 ` Nicolas Dichtel
2022-09-23 11:10 ` patchwork-bot+netdevbpf
2022-09-20 7:35 ` [PATCH] " Nicolas Dichtel
2022-09-21 7:08 ` [tun] a4d8f18ebc: ltp.ioctl03.fail kernel test robot
2022-09-21 7:48 ` Cyril Hrubis [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=YyrB0fSRu7PvNvLi@yuki \
--to=chrubis@suse.cz \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=lorenzo@google.com \
--cc=ltp@lists.linux.it \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=prohr@google.com \
/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;
as well as URLs for NNTP newsgroup(s).