From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 826] red_autotest random failures
Date: Fri, 08 Oct 2021 07:23:43 +0000 [thread overview]
Message-ID: <bug-826-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=826
Bug ID: 826
Summary: red_autotest random failures
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: cristian.dumitrescu@intel.com
Reporter: david.marchand@redhat.com
CC: dev@dpdk.org, jasvinder.singh@intel.com
Target Milestone: ---
A recent failure can be found at:
https://lab.dpdk.org/results/dashboard/patchsets/19223/
50/94 DPDK:fast-tests / red_autotest FAIL 0.86s
exit status 1
23:08:32 MALLOC_PERTURB_=116 DPDK_TEST=red_autotest
/home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test
'-l 0-15' --file-prefix=red_autotest
----------------------------------- output -----------------------------------
stdout:
RTE>>red_autotest
--------------------------------------------------------------------------------
functional test 1 : use one rte_red configuration,
increase average queue size to various levels,
compare drop rate to drop probability
avg queue size enqueued dropped drop prob %
drop rate % diff % tolerance %
6 10000 0 0.0000
0.0000 0.0000 50.0000
12 10000 0 0.0000
0.0000 0.0000 50.0000
18 10000 0 0.0000
0.0000 0.0000 50.0000
24 10000 0 0.0000
0.0000 0.0000 50.0000
30 10000 0 0.0000
0.0000 0.0000 50.0000
36 9954 46 0.4167
0.4600 0.0000 50.0000
42 9901 99 1.0417
0.9900 0.0000 50.0000
48 9831 169 1.6667
1.6900 0.0000 50.0000
54 9761 239 2.2917
2.3900 0.0000 50.0000
60 9701 299 2.9167
2.9900 0.0000 50.0000
66 9618 382 3.5417
3.8200 0.0000 50.0000
72 9581 419 4.1667
4.1900 0.0000 50.0000
78 9490 510 4.7917
5.1000 0.0000 50.0000
84 9460 540 5.4167
5.4000 0.0000 50.0000
90 9398 602 6.0417
6.0200 0.0000 50.0000
96 9371 629 6.6667
6.2900 0.0000 50.0000
102 9259 741 7.2917
7.4100 0.0000 50.0000
108 9211 789 7.9167
7.8900 0.0000 50.0000
114 9133 867 8.5417
8.6700 0.0000 50.0000
120 9058 942 9.1667
9.4200 0.0000 50.0000
126 8987 1013 9.7917
10.1300 0.0000 50.0000
132 0 10000 100.0000
100.0000 0.0000 50.0000
138 0 10000 100.0000
100.0000 0.0000 50.0000
144 0 10000 100.0000
100.0000 0.0000 50.0000
-------------------------------------<pass>-------------------------------------
--------------------------------------------------------------------------------
functional test 2 : use several RED configurations,
increase average queue size to just below maximum
threshold,
compare drop rate to drop probability
RED config avg queue size min threshold max threshold drop prob % drop
rate % diff % tolerance %
0 127 32 128 9.8958
9.9400 0.0000 50.0000
1 127 32 128 4.9479
4.8100 0.0000 50.0000
2 127 32 128 3.2986
2.6800 0.0000 50.0000
3 127 32 128 2.4740
1.6300 0.0000 50.0000
4 127 32 128 1.9792
1.2700 0.0000 50.0000
5 127 32 128 1.6493
1.0300 0.0000 50.0000
6 127 32 128 1.4137
0.8300 0.0000 50.0000
7 127 32 128 1.2370
0.7300 0.0000 50.0000
8 127 32 128 1.0995
0.6200 0.0000 50.0000
9 127 32 128 0.9896
0.5500 0.0000 50.0000
-------------------------------------<pass>-------------------------------------
--------------------------------------------------------------------------------
functional test 3 : use one RED configuration,
increase average queue size to target level,
dequeue all packets until queue is empty,
confirm that average queue size is computed correctly while
queue is empty
q avg before q avg after expected difference % tolerance %
result
1022.0000 1022.0000 1016.0627 0.5843 5.0000 pass
1022.0000 1022.0000 1016.0627 0.5843 5.0000 pass
1022.0000 1022.0000 1016.0627 0.5843 5.0000 pass
1022.0000 1022.0000 1016.0627 0.5843 5.0000 pass
1022.0000 1022.0000 1016.0627 0.5843 5.0000 pass
-------------------------------------<pass>-------------------------------------
--------------------------------------------------------------------------------
functional test 5 : use several queues (each with its own run-time data),
use several RED configurations (such that each
configuration is shared by multiple queues),
increase average queue size to just below maximum
threshold,
compare drop rate to drop probability,
(this is a larger scale version of functional test 2)
queue config avg queue size min threshold max threshold drop
prob % drop rate % diff % tolerance %
0 0 127 32 128
9.8958 9.9700 0.0000 50.0000
1 0 127 32 128
9.8958 9.7200 0.0000 50.0000
2 1 127 32 128
4.9479 4.8900 0.0000 50.0000
3 1 127 32 128
4.9479 4.8200 0.0000 50.0000
-------------------------------------<pass>-------------------------------------
--------------------------------------------------------------------------------
functional test 6 : use several queues (each with its own run-time data),
use several RED configurations (such that each
configuration is sharte_red by multiple queues),
increase average queue size to target level,
dequeue all packets until queue is empty,
confirm that average queue size is computed correctly while
queue is empty
(this is a larger scale version of functional test 3)
queue config q avg before q avg after expected
difference % tolerance % result
0 0 1022.0000 1022.0000 1016.0627
0.5843 5.0000 pass
1 0 1022.0000 1022.0000 1016.0627
0.5843 5.0000 pass
2 1 1022.0000 1022.0000 1010.1483
1.1733 5.0000 pass
3 1 1022.0000 937.1660 1010.1483
7.2249 5.0000 fail
-------------------------------------<fail>-------------------------------------
--------------------------------------------------------------------------------
overflow test 1 : use one RED configuration,
increase average queue size to target level,
check maximum number of bits requirte_red to represent avg_s
avg queue size wq_log2 fraction bits max queue avg num bits enqueued
dropped drop prob % drop rate %
1023 12 10 0xffc00000 32 0
941366 100.00 100.00
-------------------------------------<pass>-------------------------------------
[total: 6, pass: 5, fail: 1]
Test Failed
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-10-08 7:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 7:23 bugzilla [this message]
2021-11-12 13:51 ` David Marchand
2021-11-12 14:10 ` Lincoln Lavoie
2021-11-12 14:15 ` David Marchand
2021-11-15 11:51 ` Dumitrescu, Cristian
2021-11-15 17:26 ` Liguzinski, WojciechX
2021-11-18 22:10 ` Liguzinski, WojciechX
2021-11-19 7:26 ` Thomas Monjalon
2021-11-19 16:53 ` Dumitrescu, Cristian
2021-11-19 17:25 ` Lincoln Lavoie
2021-11-24 7:48 ` Liguzinski, WojciechX
2021-11-29 17:58 ` Brandon Lo
2021-11-30 7:51 ` Liguzinski, WojciechX
2021-12-10 13:31 ` Liguzinski, WojciechX
2021-11-22 8:17 ` David Marchand
2021-11-22 13:34 ` Lincoln Lavoie
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=bug-826-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).