From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andre Muezerie <andremue@linux.microsoft.com>
Subject: |FAILURE| pw149445 [PATCH] app/test: fix stack overflow in fib6_perf
Date: Mon, 23 Dec 2024 20:51:53 -0800 (PST) [thread overview]
Message-ID: <676a3de9.050a0220.2e55c8.0c44SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1734988233-20208-1-git-send-email-andremue@linux.microsoft.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/149445
_Testing issues_
Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Monday, December 23 2024 21:10:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fd51012de5369679e807be1d6a81d63ef15015ce
149445 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#301681
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 40 | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 39 | FAIL |
+---------------------+----------------+
| Fedora 39 (Clang) | PEND |
+---------------------+----------------+
| Fedora 40 (Clang) | PEND |
+---------------------+----------------+
| RHEL9 | PEND |
+---------------------+----------------+
| Fedora 41 | PEND |
+---------------------+----------------+
| RHEL8 | PEND |
+---------------------+----------------+
| Ubuntu 24.04 | PEND |
+---------------------+----------------+
| Fedora 41 (Clang) | PEND |
+---------------------+----------------+
| Ubuntu 22.04 | PEND |
+---------------------+----------------+
| Ubuntu 20.04 | PEND |
+---------------------+----------------+
| Windows Server 2022 | PEND |
+---------------------+----------------+
==== Unit test summary for Fedora 39 (dpdk_unit_test): ====
ninja: Entering directory `/root/workspace/Generic-Unit-Test-DPDK/dpdk/build'
ninja: no work to do.
1/118 DPDK:fast-tests / acl_autotest OK 2.86s
2/118 DPDK:fast-tests / alarm_autotest OK 1.18s
3/118 DPDK:fast-tests / argparse_autotest OK 0.17s
4/118 DPDK:fast-tests / atomic_autotest OK 0.33s
5/118 DPDK:fast-tests / bitcount_autotest OK 0.18s
6/118 DPDK:fast-tests / bitmap_autotest OK 0.17s
7/118 DPDK:fast-tests / bitops_autotest OK 1.68s
8/118 DPDK:fast-tests / bitratestats_autotest OK 0.18s
9/118 DPDK:fast-tests / bitset_autotest OK 1.25s
10/118 DPDK:fast-tests / bpf_autotest OK 0.18s
11/118 DPDK:fast-tests / bpf_convert_autotest OK 0.18s
12/118 DPDK:fast-tests / byteorder_autotest OK 0.18s
13/118 DPDK:fast-tests / cfgfile_autotest OK 0.18s
14/118 DPDK:fast-tests / cksum_autotest OK 0.18s
15/118 DPDK:fast-tests / cmdline_autotest OK 0.17s
16/118 DPDK:fast-tests / common_autotest OK 0.47s
17/118 DPDK:fast-tests / compressdev_autotest SKIP 0.14s exit status 77
18/118 DPDK:fast-tests / cpuflags_autotest OK 0.18s
19/118 DPDK:fast-tests / crc_autotest OK 0.18s
20/118 DPDK:fast-tests / user_delay_us OK 0.18s
21/118 DPDK:fast-tests / debug_autotest OK 0.49s
22/118 DPDK:fast-tests / devargs_autotest OK 0.18s
23/118 DPDK:fast-tests / dispatcher_autotest SKIP 0.14s exit status 77
24/118 DPDK:fast-tests / distributor_autotest OK 0.85s
25/118 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.84s
26/118 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.31s
27/118 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.48s
28/118 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.21s
29/118 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.51s
30/118 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.38s
31/118 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.33s
32/118 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.57s
33/118 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.28s
34/118 DPDK:fast-tests / eal_flags_mem_autotest OK 0.74s
35/118 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 2.09s
36/118 DPDK:fast-tests / eal_flags_misc_autotest FAIL 2.29s killed by signal 11 SIGSEGV
>>> DPDK_TEST=eal_flags_misc_autotest MALLOC_PERTURB_=8 /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test
37/118 DPDK:fast-tests / eal_fs_autotest OK 0.19s
38/118 DPDK:fast-tests / errno_autotest OK 0.18s
39/118 DPDK:fast-tests / ethdev_link_status OK 0.18s
40/118 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.45s
41/118 DPDK:fast-tests / event_ring_autotest OK 0.18s
42/118 DPDK:fast-tests / eventdev_common_autotest OK 0.18s
43/118 DPDK:fast-tests / eventdev_selftest_sw OK 0.21s
44/118 DPDK:fast-tests / fbarray_autotest OK 0.18s
45/118 DPDK:fast-tests / fib_autotest OK 0.95s
46/118 DPDK:fast-tests / fib6_autotest OK 0.78s
47/118 DPDK:fast-tests / func_reentrancy_autotest OK 0.53s
48/118 DPDK:fast-tests / graph_autotest OK 0.18s
49/118 DPDK:fast-tests / node_list_dump OK 0.18s
50/118 DPDK:fast-tests / hash_autotest OK 0.29s
51/118 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.14s exit status 77
52/118 DPDK:fast-tests / interrupt_autotest OK 1.20s
53/118 DPDK:fast-tests / ipfrag_autotest OK 0.14s
54/118 DPDK:fast-tests / ipsec_autotest SKIP 0.18s exit status 77
55/118 DPDK:fast-tests / kvargs_autotest OK 0.17s
56/118 DPDK:fast-tests / latencystats_autotest OK 0.18s
57/118 DPDK:fast-tests / lcore_var_autotest OK 0.33s
58/118 DPDK:fast-tests / lcores_autotest OK 0.70s
59/118 DPDK:fast-tests / logs_autotest OK 0.17s
60/118 DPDK:fast-tests / lpm_autotest OK 2.62s
61/118 DPDK:fast-tests / lpm6_autotest OK 4.04s
62/118 DPDK:fast-tests / malloc_autotest OK 0.37s
63/118 DPDK:fast-tests / mbuf_autotest OK 0.18s
64/118 DPDK:fast-tests / mcslock_autotest OK 0.42s
65/118 DPDK:fast-tests / member_autotest OK 0.95s
66/118 DPDK:fast-tests / memcpy_autotest OK 1.72s
67/118 DPDK:fast-tests / memory_autotest OK 0.14s
68/118 DPDK:fast-tests / mempool_autotest OK 0.43s
69/118 DPDK:fast-tests / memzone_autotest OK 0.15s
70/118 DPDK:fast-tests / meter_autotest OK 0.18s
71/118 DPDK:fast-tests / metrics_autotest OK 0.18s
72/118 DPDK:fast-tests / multiprocess_autotest OK 0.27s
73/118 DPDK:fast-tests / net_ether_autotest OK 0.47s
74/118 DPDK:fast-tests / net_ipv6_autotest OK 0.17s
75/118 DPDK:fast-tests / pcapng_autotest OK 6.81s
76/118 DPDK:fast-tests / pdcp_autotest SKIP 0.16s exit status 77
77/118 DPDK:fast-tests / pdump_autotest OK 0.45s
78/118 DPDK:fast-tests / per_lcore_autotest OK 0.32s
79/118 DPDK:fast-tests / pflock_autotest OK 0.31s
80/118 DPDK:fast-tests / pie_autotest OK 0.20s
81/118 DPDK:fast-tests / ring_pmd_autotest OK 0.20s
82/118 DPDK:fast-tests / power_autotest OK 0.19s
83/118 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.16s exit status 77
84/118 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.20s exit status 77
85/118 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.16s exit status 77
86/118 DPDK:fast-tests / prefetch_autotest OK 0.19s
87/118 DPDK:fast-tests / ptr_compress_autotest OK 0.19s
88/118 DPDK:fast-tests / rawdev_autotest OK 0.19s
89/118 DPDK:fast-tests / rcu_qsbr_autotest OK 0.31s
90/118 DPDK:fast-tests / reorder_autotest OK 0.51s
91/118 DPDK:fast-tests / rib_autotest OK 9.85s
92/118 DPDK:fast-tests / rib6_autotest OK 9.80s
93/118 DPDK:fast-tests / ring_autotest OK 0.20s
94/118 DPDK:fast-tests / rwlock_test1_autotest OK 0.34s
95/118 DPDK:fast-tests / rwlock_rda_autotest OK 5.51s
96/118 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.20s
97/118 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.17s
98/118 DPDK:fast-tests / sched_autotest OK 0.18s
99/118 DPDK:fast-tests / security_autotest OK 0.15s
100/118 DPDK:fast-tests / seqlock_autotest SKIP 0.18s exit status 77
101/118 DPDK:fast-tests / service_autotest OK 0.29s
102/118 DPDK:fast-tests / spinlock_autotest OK 0.19s
103/118 DPDK:fast-tests / stack_autotest OK 0.18s
104/118 DPDK:fast-tests / stack_lf_autotest OK 0.23s
105/118 DPDK:fast-tests / string_autotest OK 0.21s
106/118 DPDK:fast-tests / table_autotest OK 5.47s
107/118 DPDK:fast-tests / tailq_autotest OK 0.17s
108/118 DPDK:fast-tests / telemetry_data_autotest OK 0.17s
109/118 DPDK:fast-tests / telemetry_json_autotest OK 0.17s
110/118 DPDK:fast-tests / thash_autotest OK 0.19s
111/118 DPDK:fast-tests / threads_autotest OK 0.32s
112/118 DPDK:fast-tests / ticketlock_autotest OK 0.18s
113/118 DPDK:fast-tests / timer_autotest OK 2.49s
114/118 DPDK:fast-tests / trace_autotest OK 0.19s
115/118 DPDK:fast-tests / trace_autotest_with_traces OK 0.18s
116/118 DPDK:fast-tests / vdev_autotest OK 0.17s
117/118 DPDK:fast-tests / version_autotest OK 0.17s
118/118 DPDK:fast-tests / telemetry_all SKIP 0.01s exit status 77
Ok: 107
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 10
Timeout: 0
Full log written to /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
Test log output from the failed test eal_flags_misc_autotest:
Sorry, we were not able to find the logs for this test.
Download the log output from the CI site for this test run.
==== End log output ====
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Fedora 41
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Fedora 41 (Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32205/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-12-24 4:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1734988233-20208-1-git-send-email-andremue@linux.microsoft.com>
2024-12-23 20:39 ` |SUCCESS| pw149445 [PATCH] app/test: fix stack overflow in fib6_perf_autotest qemudev
2024-12-23 20:43 ` qemudev
2024-12-23 21:11 ` checkpatch
2024-12-23 22:05 ` 0-day Robot
2024-12-24 4:47 ` |SUCCESS| pw149445 [PATCH] app/test: fix stack overflow in fib6_perf dpdklab
2024-12-24 4:51 ` dpdklab [this message]
2024-12-24 4:52 ` |FAILURE| " dpdklab
2024-12-24 4:55 ` |SUCCESS| " dpdklab
2024-12-24 4:55 ` dpdklab
2024-12-24 4:57 ` dpdklab
2024-12-24 5:10 ` dpdklab
2024-12-24 5:10 ` |FAILURE| " dpdklab
2024-12-24 5:17 ` |PENDING| " dpdklab
2024-12-24 5:28 ` |SUCCESS| " dpdklab
2024-12-24 5:37 ` dpdklab
2024-12-24 5:45 ` dpdklab
2024-12-24 5:47 ` dpdklab
2024-12-24 8:44 ` dpdklab
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=676a3de9.050a0220.2e55c8.0c44SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andremue@linux.microsoft.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).