From: David Marchand <david.marchand@redhat.com>
To: huichao cai <chcchc88@163.com>
Cc: dev <dev@dpdk.org>, "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test/ipfrag: add test content to the test unit
Date: Mon, 8 Nov 2021 21:28:35 +0100 [thread overview]
Message-ID: <CAJFAV8x=WvLUunWp6jTEXw+xTQmop0mMxUojFn858tDgtc-PZA@mail.gmail.com> (raw)
In-Reply-To: <1635148739-61415-1-git-send-email-chcchc88@163.com>
On Mon, Oct 25, 2021 at 9:59 AM huichao cai <chcchc88@163.com> wrote:
>
> Add the test content of the fragment_offset(offset and MF)
> to the test_ip_frag function. Add test data for a fragment
> that is not the last fragment.
>
> Signed-off-by: huichao cai <chcchc88@163.com>
The CI raises a regression on the ip frag test.
DPDK_TEST='ipfrag_autotest'
/home/runner/work/dpdk/dpdk/build/app/test/dpdk-test
--file-prefix=ipfrag_autotest
--- stdout ---
RTE>>ipfrag_autotest^M
+ ------------------------------------------------------- +
+ Test Suite : IP Frag Unit Test Suite
+ ------------------------------------------------------- +
0: checking 2 with 2
0-0: checking 32 with 32
0-1: checking 40192 with 40192
1: checking 2 with 2
1-0: checking 32 with 32
1-1: checking 40192 with 40192
2: checking 3 with 3
2-0: checking 32 with 32
2-1: checking 18464 with 18464
2-2: checking 36864 with 36864
3: checking -22 with -22
4: checking -95 with -95
5: checking 3 with 3
5-0: checking 32 with 32
5-1: checking 18464 with 18464
5-2: checking 36864 with 36864
6: checking 3 with 3
6-0: checking 6688 with 3360
+ TestCase [ 0] : test_ip_frag failed
+ ------------------------------------------------------- +
+ Test Suite Summary : IP Frag Unit Test Suite
+ ------------------------------------------------------- +
+ Tests Total : 1
+ Tests Skipped : 0
+ Tests Executed : 1
+ Tests Unsupported: 0
+ Tests Passed : 0
+ Tests Failed : 1
+ ------------------------------------------------------- +
Test Failed
RTE>>
--- stderr ---
Please investigate, thanks.
--
David Marchand
next prev parent reply other threads:[~2021-11-08 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 7:58 huichao cai
2021-10-28 12:24 ` Ananyev, Konstantin
2021-11-10 10:46 ` David Marchand
2021-11-08 20:28 ` David Marchand [this message]
2021-11-09 2:21 ` Huichao Cai
2021-11-09 8:14 ` David Marchand
2021-11-09 9:03 ` Huichao Cai
2021-11-09 9:16 ` David Marchand
2021-11-09 9:29 ` Huichao Cai
2021-11-09 9:14 ` Huichao Cai
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='CAJFAV8x=WvLUunWp6jTEXw+xTQmop0mMxUojFn858tDgtc-PZA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=chcchc88@163.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.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).