From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Amit Prakash Shukla <amitprakashs@marvell.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw122697 [PATCH v3] eventdev: add trace points
Date: Fri, 3 Feb 2023 16:37:37 +0800 [thread overview]
Message-ID: <202302030837.3138bbup1031269@localhost.localdomain> (raw)
In-Reply-To: <20230130173006.1724832-1-amitprakashs@marvell.com>
Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/122697
_Unit Testing FAIL_
Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Mon, 30 Jan 2023 23:00:06 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: edae0bd174dc37603624bbc44fd0d4d8edeb49bf
122697 --> 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/103 DPDK:fast-tests / acl_autotest OK 2.79s
2/103 DPDK:fast-tests / atomic_autotest OK 7.06s
3/103 DPDK:fast-tests / bitmap_autotest OK 0.06s
4/103 DPDK:fast-tests / bpf_autotest OK 0.05s
5/103 DPDK:fast-tests / bpf_convert_autotest OK 0.05s
6/103 DPDK:fast-tests / bitops_autotest OK 0.05s
7/103 DPDK:fast-tests / byteorder_autotest OK 0.05s
8/103 DPDK:fast-tests / cksum_autotest OK 0.05s
9/103 DPDK:fast-tests / cmdline_autotest OK 0.06s
10/103 DPDK:fast-tests / common_autotest OK 0.89s
11/103 DPDK:fast-tests / cpuflags_autotest OK 0.05s
12/103 DPDK:fast-tests / debug_autotest OK 4.86s
13/103 DPDK:fast-tests / devargs_autotest OK 0.05s
14/103 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.60s
15/103 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.17s
16/103 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.16s
17/103 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.11s
18/103 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.17s
19/103 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.21s
20/103 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.18s
21/103 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.15s
22/103 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.14s
23/103 DPDK:fast-tests / eal_flags_mem_autotest OK 0.51s
24/103 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.22s
25/103 DPDK:fast-tests / eal_flags_misc_autotest OK 0.70s
26/103 DPDK:fast-tests / eal_fs_autotest OK 0.05s
27/103 DPDK:fast-tests / errno_autotest OK 0.05s
28/103 DPDK:fast-tests / ethdev_link_status OK 0.05s
29/103 DPDK:fast-tests / event_ring_autotest OK 0.05s
30/103 DPDK:fast-tests / fib_autotest OK 0.85s
31/103 DPDK:fast-tests / fib6_autotest OK 0.87s
32/103 DPDK:fast-tests / func_reentrancy_autotest OK 2.28s
33/103 DPDK:fast-tests / hash_autotest OK 1.02s
34/103 DPDK:fast-tests / interrupt_autotest OK 1.36s
35/103 DPDK:fast-tests / ipfrag_autotest OK 0.06s
36/103 DPDK:fast-tests / lcores_autotest OK 1.04s
37/103 DPDK:fast-tests / logs_autotest OK 0.05s
38/103 DPDK:fast-tests / lpm_autotest OK 5.92s
39/103 DPDK:fast-tests / lpm6_autotest OK 8.84s
40/103 DPDK:fast-tests / malloc_autotest OK 63.99s
41/103 DPDK:fast-tests / mbuf_autotest OK 7.07s
42/103 DPDK:fast-tests / mcslock_autotest OK 3.77s
43/103 DPDK:fast-tests / memcpy_autotest OK 6.63s
44/103 DPDK:fast-tests / memory_autotest OK 0.07s
45/103 DPDK:fast-tests / mempool_autotest OK 0.43s
46/103 DPDK:fast-tests / memzone_autotest OK 0.14s
47/103 DPDK:fast-tests / meter_autotest OK 0.05s
48/103 DPDK:fast-tests / multiprocess_autotest OK 0.14s
49/103 DPDK:fast-tests / per_lcore_autotest OK 0.15s
50/103 DPDK:fast-tests / pflock_autotest OK 0.86s
51/103 DPDK:fast-tests / prefetch_autotest OK 0.05s
52/103 DPDK:fast-tests / rcu_qsbr_autotest OK 0.57s
53/103 DPDK:fast-tests / pie_autotest OK 0.05s
54/103 DPDK:fast-tests / rib_autotest OK 10.30s
55/103 DPDK:fast-tests / rib6_autotest OK 10.29s
56/103 DPDK:fast-tests / ring_autotest OK 0.09s
57/103 DPDK:fast-tests / rwlock_test1_autotest OK 0.80s
58/103 DPDK:fast-tests / rwlock_rda_autotest OK 5.05s
59/103 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.05s
60/103 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.05s
61/103 DPDK:fast-tests / sched_autotest OK 0.04s
62/103 DPDK:fast-tests / security_autotest OK 0.05s
63/103 DPDK:fast-tests / seqlock_autotest OK 2.05s
64/103 DPDK:fast-tests / spinlock_autotest OK 0.13s
65/103 DPDK:fast-tests / stack_autotest OK 0.85s
66/103 DPDK:fast-tests / stack_lf_autotest SKIP 0.05s exit status 77
67/103 DPDK:fast-tests / string_autotest OK 0.05s
68/103 DPDK:fast-tests / tailq_autotest OK 0.05s
69/103 DPDK:fast-tests / ticketlock_autotest OK 0.21s
70/103 DPDK:fast-tests / timer_autotest OK 3.93s
71/103 DPDK:fast-tests / user_delay_us OK 0.06s
72/103 DPDK:fast-tests / version_autotest OK 0.05s
73/103 DPDK:fast-tests / crc_autotest OK 0.05s
74/103 DPDK:fast-tests / distributor_autotest OK 1.19s
75/103 DPDK:fast-tests / eventdev_common_autotest FAIL 1.29s exit status -11
76/103 DPDK:fast-tests / fbarray_autotest OK 0.07s
77/103 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.50s
78/103 DPDK:fast-tests / ipsec_autotest SKIP 0.06s exit status 77
79/103 DPDK:fast-tests / kni_autotest SKIP 0.05s exit status 77
80/103 DPDK:fast-tests / kvargs_autotest OK 0.06s
81/103 DPDK:fast-tests / member_autotest OK 1.29s
82/103 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.05s exit status 77
83/103 DPDK:fast-tests / power_autotest OK 0.05s
84/103 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.05s exit status 77
85/103 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.05s exit status 77
86/103 DPDK:fast-tests / reorder_autotest OK 0.10s
87/103 DPDK:fast-tests / service_autotest OK 3.32s
88/103 DPDK:fast-tests / thash_autotest OK 0.05s
89/103 DPDK:fast-tests / threads_autotest OK 0.22s
90/103 DPDK:fast-tests / trace_autotest OK 0.05s
91/103 DPDK:fast-tests / trace_autotest_with_traces OK 0.08s
92/103 DPDK:fast-tests / metrics_autotest OK 0.06s
93/103 DPDK:fast-tests / telemetry_json_autotest OK 0.05s
94/103 DPDK:fast-tests / telemetry_data_autotest OK 0.06s
95/103 DPDK:fast-tests / table_autotest OK 10.16s
96/103 DPDK:fast-tests / ring_pmd_autotest OK 0.05s
97/103 DPDK:fast-tests / event_eth_tx_adapter_autotest FAIL 1.37s exit status -11
98/103 DPDK:fast-tests / bitratestats_autotest OK 0.05s
99/103 DPDK:fast-tests / latencystats_autotest OK 0.05s
100/103 DPDK:fast-tests / pdump_autotest OK 5.14s
101/103 DPDK:fast-tests / vdev_autotest OK 0.05s
102/103 DPDK:fast-tests / compressdev_autotest SKIP 0.05s exit status 77
103/103 DPDK:fast-tests / telemetry_all OK 14.48s
Ok: 94
Expected Fail: 0
Fail: 2
Unexpected Pass: 0
Skipped: 7
Timeout: 0
Test logs for failed test cases:
================================================================================
DPDK:fast-tests / eventdev_common_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>eventdev_common_autotest
-------------------------------------stderr-------------------------------------
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/eventdev_common_autotest/mp_socket
EAL: Selected IOVA mode 'PA'
TELEMETRY: No legacy callbacks, legacy socket not created
APP: HPET is not enabled, using TSC as default timer
PMD: Initializing event_skeleton on NUMA node 0
EVENTDEV: rte_event_dev_socket_id() line 78: Invalid dev_id=16
================================================================================
DPDK:fast-tests / event_eth_tx_adapter_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>event_eth_tx_adapter_autotest
-------------------------------------stderr-------------------------------------
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/event_eth_tx_adapter_autotest/mp_socket
EAL: Selected IOVA mode 'PA'
TELEMETRY: No legacy callbacks, legacy socket not created
APP: HPET is not enabled, using TSC as default timer
next prev parent reply other threads:[~2023-02-03 8:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230130173006.1724832-1-amitprakashs@marvell.com>
2023-01-30 17:23 ` |SUCCESS| " qemudev
2023-01-30 17:27 ` |FAILURE| " qemudev
2023-01-30 17:31 ` |SUCCESS| " checkpatch
2023-01-30 18:19 ` |FAILURE| " 0-day Robot
2023-02-03 8:33 ` |SUCCESS| " qemudev
2023-02-03 8:37 ` qemudev [this message]
2023-01-30 18:02 |FAILURE| pw122697 [PATCH] [v3] " dpdklab
2023-01-30 18:02 dpdklab
2023-01-30 18:17 dpdklab
2023-01-30 22:23 dpdklab
2023-01-30 22:24 dpdklab
2023-01-30 22:25 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:27 dpdklab
2023-01-30 22:58 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=202302030837.3138bbup1031269@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=amitprakashs@marvell.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).