From: Vipin P R <vipinp@vmware.com>
To: anatoly.burakov@intel.com
Cc: dev@dpdk.org, Vipin P R <vipinp@vmware.com>
Subject: [PATCH] *** Memory Allocation: Adding a new UT for fb_array ***
Date: Fri, 13 Jan 2023 13:12:46 +0000 [thread overview]
Message-ID: <1673615567-20873-1-git-send-email-vipinp@vmware.com> (raw)
***
Partial output of fbarray_autotest (app/test/dpdk-test --log-level="*:debug") [WITHOUT THE FIX]
..
..
EAL: ms_idx:1096
EAL: ms_idx:1097
EAL: ms_idx:1098
EAL: ms_idx:1099
EAL: ms_idx:1155
EAL: ms_idx:1156
EAL: ms_idx:1158
EAL: ms_idx:1159
EAL: ms_idx:1154
EAL: ms_idx jumping behind. ms_idx: 1154 prev_ms_idx: 1159
EAL: Test assert test_jump line 445 failed: Incorrect ms_idx jump
+ TestCase [ 2] : test_jump failed
+ TestCase [ 3] : test_find succeeded
+ TestCase [ 4] : test_find succeeded
+ TestCase [ 5] : test_find succeeded
+ TestCase [ 6] : test_find succeeded
+ TestCase [ 7] : test_find succeeded
+ TestCase [ 8] : test_empty succeeded
+ ------------------------------------------------------- +
+ Test Suite Summary
+ Tests Total : 9
+ Tests Skipped : 0
+ Tests Executed : 9
+ Tests Unsupported: 0
+ Tests Passed : 8
+ Tests Failed : 1
+ ------------------------------------------------------- +
Test Failed
RTE>>
Partial output of fbarray_autotest (app/test/dpdk-test --log-level="*:debug") [WITH THE FIX]
..
..
EAL: ms_idx:1109
EAL: ms_idx:1110
EAL: ms_idx:1112
+ TestCase [ 2] : test_jump succeeded
+ TestCase [ 3] : test_find succeeded
+ TestCase [ 4] : test_find succeeded
+ TestCase [ 5] : test_find succeeded
+ TestCase [ 6] : test_find succeeded
+ TestCase [ 7] : test_find succeeded
+ TestCase [ 8] : test_empty succeeded
+ ------------------------------------------------------- +
+ Test Suite Summary
+ Tests Total : 9
+ Tests Skipped : 0
+ Tests Executed : 9
+ Tests Unsupported: 0
+ Tests Passed : 9
+ Tests Failed : 0
+ ------------------------------------------------------- +
Test OK
RTE>>
***
Vipin P R (1):
Memory Allocation: Adding a new UT for fb_array
app/test/test_fbarray.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
--
2.7.4
next reply other threads:[~2023-01-15 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 13:12 Vipin P R [this message]
2023-01-13 13:12 ` [PATCH] Memory Allocation: Adding a new UT for fb_array Vipin P R
2023-01-16 17:54 ` Stephen Hemminger
2023-05-16 13:39 ` Burakov, Anatoly
2023-05-16 14:25 ` Burakov, Anatoly
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=1673615567-20873-1-git-send-email-vipinp@vmware.com \
--to=vipinp@vmware.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
/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).