From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: luca.boccassi@gmail.com, zhoumin@loongson.cn
Subject: |FAILURE| pw135858 [PATCH] test: move lcores/pdump/pflock/ticketlock out of fast suite
Date: Mon, 15 Jan 2024 13:52:21 +0800 [thread overview]
Message-ID: <202401150552.40F5qL1A220247@localhost.localdomain> (raw)
In-Reply-To: <20240112201056.452598-1-luca.boccassi@gmail.com>
Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/135858
_Unit Testing FAIL_
Submitter: Luca Boccassi <luca.boccassi@gmail.com>
Date: Fri, 12 Jan 2024 20:10:56 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: d4af9a82063e4c39568191eaa12955d3ca39581a
135858 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+---------------------+----------------+
| Loongnix-Server 8.3 | FAIL |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
Test result details:
1/107 DPDK:fast-tests / acl_autotest OK 3.38s
2/107 DPDK:fast-tests / atomic_autotest OK 7.18s
3/107 DPDK:fast-tests / bitcount_autotest OK 0.47s
4/107 DPDK:fast-tests / bitmap_autotest OK 0.47s
5/107 DPDK:fast-tests / bitops_autotest OK 0.47s
6/107 DPDK:fast-tests / bitratestats_autotest OK 0.47s
7/107 DPDK:fast-tests / bpf_autotest OK 0.47s
8/107 DPDK:fast-tests / bpf_convert_autotest OK 0.47s
9/107 DPDK:fast-tests / byteorder_autotest OK 0.47s
10/107 DPDK:fast-tests / cksum_autotest OK 0.47s
11/107 DPDK:fast-tests / cmdline_autotest OK 0.57s
12/107 DPDK:fast-tests / common_autotest OK 1.52s
13/107 DPDK:fast-tests / compressdev_autotest SKIP 0.12s exit status 77
14/107 DPDK:fast-tests / cpuflags_autotest OK 0.47s
15/107 DPDK:fast-tests / crc_autotest OK 0.47s
16/107 DPDK:fast-tests / user_delay_us OK 0.47s
17/107 DPDK:fast-tests / debug_autotest OK 26.74s
18/107 DPDK:fast-tests / devargs_autotest OK 0.47s
19/107 DPDK:fast-tests / dispatcher_autotest OK 2.57s
20/107 DPDK:fast-tests / distributor_autotest OK 1.27s
21/107 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.18s
22/107 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
23/107 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
24/107 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
25/107 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
26/107 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
27/107 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
28/107 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
29/107 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
30/107 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
31/107 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 3.33s
32/107 DPDK:fast-tests / eal_flags_misc_autotest OK 1.12s
33/107 DPDK:fast-tests / eal_fs_autotest OK 0.47s
34/107 DPDK:fast-tests / errno_autotest OK 0.47s
35/107 DPDK:fast-tests / ethdev_link_status OK 0.47s
36/107 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
37/107 DPDK:fast-tests / event_ring_autotest OK 0.47s
38/107 DPDK:fast-tests / eventdev_common_autotest OK 0.47s
39/107 DPDK:fast-tests / eventdev_selftest_sw OK 7.43s
40/107 DPDK:fast-tests / fbarray_autotest OK 0.47s
41/107 DPDK:fast-tests / fib_autotest OK 1.17s
42/107 DPDK:fast-tests / fib6_autotest OK 1.17s
43/107 DPDK:fast-tests / func_reentrancy_autotest OK 7.43s
44/107 DPDK:fast-tests / graph_autotest OK 0.37s
45/107 DPDK:fast-tests / node_list_dump OK 0.57s
46/107 DPDK:fast-tests / hash_autotest OK 1.27s
47/107 DPDK:fast-tests / hash_readwrite_func_autotest FAIL 0.22s exit status 255
48/107 DPDK:fast-tests / interrupt_autotest OK 1.62s
49/107 DPDK:fast-tests / ipfrag_autotest OK 0.12s
50/107 DPDK:fast-tests / ipsec_autotest SKIP 0.32s exit status 77
51/107 DPDK:fast-tests / kvargs_autotest OK 0.32s
52/107 DPDK:fast-tests / latencystats_autotest OK 0.32s
53/107 DPDK:fast-tests / logs_autotest OK 0.32s
54/107 DPDK:fast-tests / lpm_autotest OK 2.38s
55/107 DPDK:fast-tests / lpm6_autotest OK 5.49s
56/107 DPDK:fast-tests / malloc_autotest OK 62.47s
57/107 DPDK:fast-tests / mbuf_autotest OK 4.93s
58/107 DPDK:fast-tests / mcslock_autotest OK 3.47s
59/107 DPDK:fast-tests / member_autotest OK 1.62s
60/107 DPDK:fast-tests / memcpy_autotest OK 7.18s
61/107 DPDK:fast-tests / memory_autotest OK 0.12s
62/107 DPDK:fast-tests / mempool_autotest OK 0.47s
63/107 DPDK:fast-tests / memzone_autotest OK 0.17s
64/107 DPDK:fast-tests / meter_autotest OK 0.32s
65/107 DPDK:fast-tests / metrics_autotest OK 0.32s
66/107 DPDK:fast-tests / multiprocess_autotest OK 0.27s
67/107 DPDK:fast-tests / net_ether_autotest OK 1.02s
68/107 DPDK:fast-tests / pcapng_autotest OK 6.38s
69/107 DPDK:fast-tests / pdcp_autotest SKIP 0.12s exit status 77
70/107 DPDK:fast-tests / per_lcore_autotest OK 0.47s
71/107 DPDK:fast-tests / pie_autotest OK 0.37s
72/107 DPDK:fast-tests / ring_pmd_autotest OK 0.32s
73/107 DPDK:fast-tests / power_autotest OK 0.32s
74/107 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
75/107 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.32s exit status 77
76/107 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
77/107 DPDK:fast-tests / prefetch_autotest OK 0.32s
78/107 DPDK:fast-tests / rawdev_autotest OK 0.32s
79/107 DPDK:fast-tests / rcu_qsbr_autotest OK 0.87s
80/107 DPDK:fast-tests / reorder_autotest OK 0.42s
81/107 DPDK:fast-tests / rib_autotest OK 8.99s
82/107 DPDK:fast-tests / rib6_autotest OK 8.98s
83/107 DPDK:fast-tests / ring_autotest OK 0.37s
84/107 DPDK:fast-tests / rwlock_test1_autotest OK 1.12s
85/107 DPDK:fast-tests / rwlock_rda_autotest OK 5.33s
86/107 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.33s
87/107 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.33s
88/107 DPDK:fast-tests / sched_autotest OK 0.32s
89/107 DPDK:fast-tests / security_autotest OK 0.07s
90/107 DPDK:fast-tests / seqlock_autotest OK 2.32s
91/107 DPDK:fast-tests / service_autotest OK 3.07s
92/107 DPDK:fast-tests / spinlock_autotest OK 0.42s
93/107 DPDK:fast-tests / stack_autotest OK 0.87s
94/107 DPDK:fast-tests / stack_lf_autotest SKIP 0.12s exit status 77
95/107 DPDK:fast-tests / string_autotest OK 0.32s
96/107 DPDK:fast-tests / table_autotest OK 7.64s
97/107 DPDK:fast-tests / tailq_autotest OK 0.32s
98/107 DPDK:fast-tests / telemetry_data_autotest OK 0.32s
99/107 DPDK:fast-tests / telemetry_json_autotest OK 0.32s
100/107 DPDK:fast-tests / thash_autotest OK 0.32s
101/107 DPDK:fast-tests / threads_autotest OK 0.52s
102/107 DPDK:fast-tests / timer_autotest OK 3.92s
103/107 DPDK:fast-tests / trace_autotest OK 0.32s
104/107 DPDK:fast-tests / trace_autotest_with_traces OK 0.37s
105/107 DPDK:fast-tests / vdev_autotest OK 0.32s
106/107 DPDK:fast-tests / version_autotest OK 0.32s
107/107 DPDK:fast-tests / telemetry_all OK 1.27s
Ok: 99
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 7
Timeout: 0
Test logs for failed test cases:
================================================================================
DPDK:fast-tests / hash_readwrite_func_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>hash_readwrite_func_autotest
Hardware transactional memory (lock elision) is NOT supported
Test read-write without Hardware transactional memory
hash creation failed
Test Failed
RTE>>
-------------------------------------stderr-------------------------------------
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
TMTY: TELEMETRY: No legacy callbacks, legacy socket not created
APP: HPET is not enabled, using TSC as default timer
HASH: memory allocation failed
next prev parent reply other threads:[~2024-01-15 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240112201056.452598-1-luca.boccassi@gmail.com>
2024-01-12 20:11 ` |WARNING| " checkpatch
2024-01-12 21:05 ` |SUCCESS| " 0-day Robot
2024-01-15 5:48 ` qemudev
2024-01-15 5:52 ` qemudev [this message]
2024-01-15 7:11 ` qemudev
2024-01-15 7:15 ` qemudev
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=202401150552.40F5qL1A220247@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=luca.boccassi@gmail.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).