From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1546] fib6 perf test failing
Date: Tue, 17 Sep 2024 20:41:21 +0000 [thread overview]
Message-ID: <bug-1546-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 5232 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1546
Bug ID: 1546
Summary: fib6 perf test failing
Product: DPDK
Version: 24.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Fib6 perf test is failing now
=================================== 85/193 ===================================
test: DPDK:perf-tests / fib6_perf_autotest
start time: 20:35:49
duration: 0.38s
result: (exit status 255 or signal 127 SIGinvalid)
command: DPDK_TEST=fib6_perf_autotest
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
MESON_TEST_ITERATION=1 MALLOC_PERTURB_=235
/home/shemminger/DPDK/log/build/app/dpdk-test
----------------------------------- stdout -----------------------------------
RTE>>fib6_perf_autotest
No. routes = 1000
Route distribution per prefix width:
DEPTH QUANTITY (PERCENT)
---------------------------
01 5 (0.50)
02 8 (0.80)
03 9 (0.90)
04 10 (1.00)
05 8 (0.80)
06 4 (0.40)
07 5 (0.50)
08 10 (1.00)
09 13 (1.30)
10 11 (1.10)
11 10 (1.00)
12 4 (0.40)
13 10 (1.00)
14 8 (0.80)
15 4 (0.40)
16 11 (1.10)
17 7 (0.70)
18 9 (0.90)
19 10 (1.00)
20 5 (0.50)
21 6 (0.60)
22 11 (1.10)
23 5 (0.50)
24 11 (1.10)
25 5 (0.50)
26 8 (0.80)
27 8 (0.80)
28 13 (1.30)
29 9 (0.90)
30 8 (0.80)
31 6 (0.60)
32 11 (1.10)
33 10 (1.00)
34 9 (0.90)
35 3 (0.30)
36 8 (0.80)
37 5 (0.50)
38 8 (0.80)
39 6 (0.60)
40 9 (0.90)
41 8 (0.80)
42 10 (1.00)
43 4 (0.40)
44 6 (0.60)
45 9 (0.90)
46 11 (1.10)
47 14 (1.40)
48 5 (0.50)
49 9 (0.90)
50 13 (1.30)
51 13 (1.30)
52 8 (0.80)
53 6 (0.60)
54 11 (1.10)
55 12 (1.20)
56 6 (0.60)
57 8 (0.80)
58 9 (0.90)
59 6 (0.60)
60 5 (0.50)
61 4 (0.40)
62 12 (1.20)
63 8 (0.80)
64 7 (0.70)
65 3 (0.30)
66 7 (0.70)
67 17 (1.70)
68 11 (1.10)
69 3 (0.30)
70 9 (0.90)
71 7 (0.70)
72 9 (0.90)
73 5 (0.50)
74 5 (0.50)
75 4 (0.40)
76 4 (0.40)
77 4 (0.40)
78 10 (1.00)
79 9 (0.90)
80 6 (0.60)
81 5 (0.50)
82 5 (0.50)
83 4 (0.40)
84 10 (1.00)
85 6 (0.60)
86 8 (0.80)
87 9 (0.90)
88 7 (0.70)
89 9 (0.90)
90 9 (0.90)
91 9 (0.90)
92 9 (0.90)
93 12 (1.20)
94 6 (0.60)
95 8 (0.80)
96 18 (1.80)
97 5 (0.50)
98 8 (0.80)
99 5 (0.50)
100 5 (0.50)
101 5 (0.50)
102 4 (0.40)
103 7 (0.70)
104 7 (0.70)
105 4 (0.40)
106 6 (0.60)
107 7 (0.70)
108 11 (1.10)
109 11 (1.10)
110 6 (0.60)
111 9 (0.90)
112 9 (0.90)
113 10 (1.00)
114 10 (1.00)
115 4 (0.40)
116 8 (0.80)
117 9 (0.90)
118 10 (1.00)
119 7 (0.70)
120 8 (0.80)
121 10 (1.00)
122 7 (0.70)
123 5 (0.50)
124 6 (0.60)
125 4 (0.40)
126 5 (0.50)
127 10 (1.00)
128 7 (0.70)
Error at line 97:
Test Failed
RTE>>
----------------------------------- stderr -----------------------------------
EAL: Detected CPU lcores: 8
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
APP: HPET is not enabled, using TSC as default timer
FIB: FIB dataplane struct test_fib6_perf memory allocation failed
==============================================================================
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 7094 bytes --]
reply other threads:[~2024-09-17 20:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1546-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.