From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>, zhoumin@loongson.cn
Subject: |FAILURE| pw138771-138784 [PATCH v12 14/14] maintainers: add for log library
Date: Tue, 26 Mar 2024 04:38:28 +0800 [thread overview]
Message-ID: <202403252038.42PKcSFC2624406@localhost.localdomain> (raw)
In-Reply-To: <20240325205405.669897-15-stephen@networkplumber.org>
Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/138784
_Unit Testing FAIL_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 25 Mar 2024 13:46:58 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 0b82b5139fefe6eb5ec1a0b489fd193e8a99ab73
138771-138784 --> 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/112 DPDK:fast-tests / acl_autotest OK 3.38s
2/112 DPDK:fast-tests / argparse_autotest OK 0.62s
3/112 DPDK:fast-tests / atomic_autotest OK 8.78s
4/112 DPDK:fast-tests / bitcount_autotest OK 0.42s
5/112 DPDK:fast-tests / bitmap_autotest OK 0.42s
6/112 DPDK:fast-tests / bitops_autotest OK 0.42s
7/112 DPDK:fast-tests / bitratestats_autotest OK 0.42s
8/112 DPDK:fast-tests / bpf_autotest OK 0.42s
9/112 DPDK:fast-tests / bpf_convert_autotest OK 0.42s
10/112 DPDK:fast-tests / byteorder_autotest OK 0.42s
11/112 DPDK:fast-tests / cksum_autotest OK 0.42s
12/112 DPDK:fast-tests / cmdline_autotest OK 0.42s
13/112 DPDK:fast-tests / common_autotest OK 1.27s
14/112 DPDK:fast-tests / compressdev_autotest SKIP 0.12s exit status 77
15/112 DPDK:fast-tests / cpuflags_autotest OK 0.42s
16/112 DPDK:fast-tests / crc_autotest OK 0.42s
17/112 DPDK:fast-tests / user_delay_us OK 0.42s
18/112 DPDK:fast-tests / debug_autotest OK 11.75s
19/112 DPDK:fast-tests / devargs_autotest OK 0.42s
20/112 DPDK:fast-tests / dispatcher_autotest OK 2.47s
21/112 DPDK:fast-tests / distributor_autotest OK 1.22s
22/112 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.12s
23/112 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
24/112 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
25/112 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
26/112 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
27/112 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
28/112 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
29/112 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
30/112 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
31/112 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
32/112 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.36s
33/112 DPDK:fast-tests / eal_flags_misc_autotest FAIL 0.32s exit status 255
34/112 DPDK:fast-tests / eal_fs_autotest OK 0.42s
35/112 DPDK:fast-tests / errno_autotest OK 0.42s
36/112 DPDK:fast-tests / ethdev_link_status OK 0.42s
37/112 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
38/112 DPDK:fast-tests / event_ring_autotest OK 0.42s
39/112 DPDK:fast-tests / eventdev_common_autotest OK 0.42s
40/112 DPDK:fast-tests / eventdev_selftest_sw OK 7.38s
41/112 DPDK:fast-tests / fbarray_autotest OK 0.42s
42/112 DPDK:fast-tests / fib_autotest OK 1.07s
43/112 DPDK:fast-tests / fib6_autotest OK 1.12s
44/112 DPDK:fast-tests / func_reentrancy_autotest OK 2.28s
45/112 DPDK:fast-tests / graph_autotest OK 0.42s
46/112 DPDK:fast-tests / node_list_dump OK 0.42s
47/112 DPDK:fast-tests / hash_autotest OK 1.17s
48/112 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.44s
49/112 DPDK:fast-tests / interrupt_autotest OK 1.72s
50/112 DPDK:fast-tests / ipfrag_autotest OK 0.12s
51/112 DPDK:fast-tests / ipsec_autotest SKIP 0.42s exit status 77
52/112 DPDK:fast-tests / kvargs_autotest OK 0.42s
53/112 DPDK:fast-tests / latencystats_autotest OK 0.42s
54/112 DPDK:fast-tests / lcores_autotest OK 5.23s
55/112 DPDK:fast-tests / logs_autotest OK 0.42s
56/112 DPDK:fast-tests / lpm_autotest OK 2.48s
57/112 DPDK:fast-tests / lpm6_autotest OK 5.64s
58/112 DPDK:fast-tests / malloc_autotest OK 61.35s
59/112 DPDK:fast-tests / mbuf_autotest OK 4.92s
60/112 DPDK:fast-tests / mcslock_autotest OK 4.17s
61/112 DPDK:fast-tests / member_autotest OK 1.62s
62/112 DPDK:fast-tests / memcpy_autotest OK 7.03s
63/112 DPDK:fast-tests / memory_autotest OK 0.12s
64/112 DPDK:fast-tests / mempool_autotest OK 0.47s
65/112 DPDK:fast-tests / memzone_autotest OK 0.17s
66/112 DPDK:fast-tests / meter_autotest OK 0.42s
67/112 DPDK:fast-tests / metrics_autotest OK 0.42s
68/112 DPDK:fast-tests / multiprocess_autotest OK 0.27s
69/112 DPDK:fast-tests / net_ether_autotest OK 1.07s
70/112 DPDK:fast-tests / pcapng_autotest OK 7.23s
71/112 DPDK:fast-tests / pdcp_autotest SKIP 0.12s exit status 77
72/112 DPDK:fast-tests / pdump_autotest OK 0.57s
73/112 DPDK:fast-tests / per_lcore_autotest OK 0.52s
74/112 DPDK:fast-tests / pflock_autotest OK 1.22s
75/112 DPDK:fast-tests / pie_autotest OK 0.42s
76/112 DPDK:fast-tests / ring_pmd_autotest OK 0.42s
77/112 DPDK:fast-tests / power_autotest OK 0.42s
78/112 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.12s exit status 77
79/112 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.42s exit status 77
80/112 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.12s exit status 77
81/112 DPDK:fast-tests / prefetch_autotest OK 0.42s
82/112 DPDK:fast-tests / rawdev_autotest OK 0.42s
83/112 DPDK:fast-tests / rcu_qsbr_autotest OK 0.97s
84/112 DPDK:fast-tests / reorder_autotest OK 0.47s
85/112 DPDK:fast-tests / rib_autotest OK 9.09s
86/112 DPDK:fast-tests / rib6_autotest OK 9.09s
87/112 DPDK:fast-tests / ring_autotest OK 0.47s
88/112 DPDK:fast-tests / rwlock_test1_autotest OK 1.17s
89/112 DPDK:fast-tests / rwlock_rda_autotest OK 5.43s
90/112 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.43s
91/112 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.43s
92/112 DPDK:fast-tests / sched_autotest OK 0.42s
93/112 DPDK:fast-tests / security_autotest OK 0.12s
94/112 DPDK:fast-tests / seqlock_autotest OK 2.42s
95/112 DPDK:fast-tests / service_autotest OK 3.12s
96/112 DPDK:fast-tests / spinlock_autotest OK 0.52s
97/112 DPDK:fast-tests / stack_autotest OK 0.87s
98/112 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
99/112 DPDK:fast-tests / string_autotest OK 0.42s
100/112 DPDK:fast-tests / table_autotest OK 7.89s
101/112 DPDK:fast-tests / tailq_autotest OK 0.42s
102/112 DPDK:fast-tests / telemetry_data_autotest OK 0.42s
103/112 DPDK:fast-tests / telemetry_json_autotest OK 0.42s
104/112 DPDK:fast-tests / thash_autotest OK 0.42s
105/112 DPDK:fast-tests / threads_autotest OK 0.62s
106/112 DPDK:fast-tests / ticketlock_autotest OK 0.57s
107/112 DPDK:fast-tests / timer_autotest OK 3.97s
108/112 DPDK:fast-tests / trace_autotest OK 0.42s
109/112 DPDK:fast-tests / trace_autotest_with_traces OK 0.42s
110/112 DPDK:fast-tests / vdev_autotest OK 0.42s
111/112 DPDK:fast-tests / version_autotest OK 0.42s
112/112 DPDK:fast-tests / telemetry_all OK 1.32s
Ok: 104
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 7
Timeout: 0
Test logs for failed test cases:
================================================================================
DPDK:fast-tests / eal_flags_misc_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>eal_flags_misc_autotest
Running binary with argv[]:'/home/zhoumin/gh_dpdk/build/app/dpdk-test' '--file-prefix=rte' '--proc-type=secondary' '--invalid-opt'
Usage: /home/zhoumin/gh_dpdk/build/app/dpdk-test [options]
EAL common options:
-c COREMASK Hexadecimal bitmask of cores to run on
-l CORELIST List of cores to run on
The argument format is <c1>[-c2][,c3[-c4],...]
where c1, c2, etc are core indexes between 0 and 64
--lcores COREMAP Map lcore set to physical cpu set
The argument format is
'<lcores[@cpus]>[<,lcores[@cpus]>...]'
lcores and cpus list are grouped by '(' and ')'
Within the group, '-' is used for range separator,
',' is used for single number separator.
'( )' can be omitted for single element group,
'@' can be omitted if cpus and lcores have the same value
-s SERVICE COREMASK Hexadecimal bitmask of cores to be used as service cores
--main-lcore ID Core ID that is used as main
--mbuf-pool-ops-name Pool ops name for mbuf to use
-n CHANNELS Number of memory channels
-m MB Memory to allocate (see also --socket-mem)
-r RANKS Force number of memory ranks (don't detect)
-b, --block Add a device to the blocked list.
Prevent EAL from using this device. The argument
format for PCI devices is <domain:bus:devid.func>.
-a, --allow Add a device to the allow list.
Only use the specified devices. The argument format
for PCI devices is <[domain:]bus:devid.func>.
This option can be present several times.
[NOTE: allow cannot be used with block option]
--vdev Add a virtual device.
The argument format is <driver><id>[,key=val,...]
(ex: --vdev=net_pcap0,iface=eth2).
--iova-mode Set IOVA mode. 'pa' for IOVA_PA
'va' for IOVA_VA
-d LIB.so|DIR Add a driver or driver directory
(can be used multiple times)
--vmware-tsc-map Use VMware TSC map instead of native RDTSC
--proc-type Type of this process (primary|secondary|auto)
--syslog Set syslog facility
--log-level=<level> Set global log level
--log-level=<type-match>:<level>
Set specific log level
--log-level=help Show log types and levels
--log-timestamp Timestamp log output
--trace=<regex-match>
Enable trace based on regular expression trace name.
By default, the trace is disabled.
User must specify this option to enable trace.
--trace-dir=<directory path>
Specify trace directory for trace output.
By default, trace output will created at
$HOME directory and parameter must be
specified once only.
--trace-bufsz=<int>
Specify maximum size of allocated memory
for trace output for each thread. Valid
unit can be either 'B|K|M' for 'Bytes',
'KBytes' and 'MBytes' respectively.
Default is 1MB and parameter must be
specified once only.
--trace-mode=<o[verwrite] | d[iscard]>
Specify the mode of update of trace
output file. Either update on a file can
be wrapped or discarded when file size
reaches its maximum limit.
Default mode is 'overwrite' and parameter
must be specified once only.
-v Display version information on startup
-h, --help This help
--in-memory Operate entirely in memory. This will
disable secondary process support
--base-virtaddr Base virtual address
--telemetry Enable telemetry support (on by default)
--no-telemetry Disable telemetry support
--force-max-simd-bitwidth Force the max SIMD bitwidth
EAL options for DEBUG use only:
--huge-unlink[=existing|always|never]
When to unlink files in hugetlbfs
('existing' by default, no value means 'always')
--no-huge Use malloc instead of hugetlbfs
--no-pci Disable PCI
--no-hpet Disable HPET
--no-shconf No shared config (mmap'd files)
EAL Linux options:
--socket-mem Memory to allocate on sockets (comma separated values)
--socket-limit Limit memory allocation on sockets (comma separated values)
--huge-dir Directory where hugetlbfs is mounted
--file-prefix Prefix for hugepage filenames
--create-uio-dev Create /dev/uioX (usually done by hotplug)
--vfio-intr Interrupt mode for VFIO (legacy|msi|msix)
--vfio-vf-token VF token (UUID) shared between SR-IOV PF and VFs
--legacy-mem Legacy memory mode (no dynamic allocation, contiguous segments)
--single-file-segments Put all hugepage memory in single files
--match-allocations Free hugepages exactly as allocated
--huge-worker-stack[=size]
Allocate worker thread stacks from hugepage memory.
Size is in units of kbytes and defaults to system
thread stack size if not specified.
Running binary with argv[]:'/home/zhoumin/gh_dpdk/build/app/dpdk-test' '--file-prefix=rte' '--proc-type=secondary' '--no-pci'
Running binary with argv[]:'/home/zhoumin/gh_dpdk/build/app/dpdk-test' '--file-prefix=rte' '--proc-type=secondary' '-v'
Running binary with argv[]:'/home/zhoumin/gh_dpdk/build/app/dpdk-test' '-m' '18' '--no-shconf' '--file-prefix=noshconf' '--no-huge'
Running binary with argv[]:'/home/zhoumin/gh_dpdk/build/app/dpdk-test' '--file-prefix=rte' '--proc-type=secondary' '--syslog' 'syslog'
Running binary with argv[]:'/home/zhoumin/gh_dpdk/build/app/dpdk-test' '--file-prefix=rte' '--proc-type=secondary' '--syslog'
Error - process run ok with empty --syslog flag
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'
TELEMETRY: No legacy callbacks, legacy socket not created
APP: HPET is not enabled, using TSC as default timer
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
/home/zhoumin/gh_dpdk/build/app/dpdk-test: unrecognized option '--invalid-opt'
EAL: Invalid 'command line' arguments.
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_2623292_22bbde7a0fd99
EAL: Selected IOVA mode 'PA'
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
EAL: RTE Version: 'DPDK 24.03.0-rc4'
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_2623295_22bbde7df373e
EAL: Selected IOVA mode 'PA'
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
EAL: Detected static linkage of DPDK
EAL: Selected IOVA mode 'VA'
TELEMETRY: No legacy callbacks, legacy socket not created
next prev parent reply other threads:[~2024-03-25 21:03 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240325205405.669897-15-stephen@networkplumber.org>
2024-03-25 20:34 ` |SUCCESS| " qemudev
2024-03-25 20:38 ` qemudev [this message]
2024-03-25 20:56 ` |SUCCESS| pw138784 " checkpatch
2024-03-25 21:37 ` |FAILURE| pw138771-138784 [PATCH] [v12,14/14] maintainers: add for l dpdklab
2024-03-25 21:37 ` dpdklab
2024-03-25 21:37 ` dpdklab
2024-03-25 21:37 ` dpdklab
2024-03-25 21:38 ` |SUCCESS| " dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:38 ` |FAILURE| " dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:39 ` |SUCCESS| " dpdklab
2024-03-25 21:39 ` |FAILURE| " dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:40 ` |SUCCESS| " dpdklab
2024-03-25 21:40 ` |FAILURE| " dpdklab
2024-03-25 21:40 ` dpdklab
2024-03-25 21:40 ` dpdklab
2024-03-25 21:40 ` |SUCCESS| " dpdklab
2024-03-25 21:40 ` |FAILURE| " dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:41 ` |SUCCESS| " dpdklab
2024-03-25 21:41 ` |FAILURE| " dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:42 ` dpdklab
2024-03-25 21:42 ` dpdklab
2024-03-25 21:42 ` dpdklab
2024-03-25 21:42 ` |SUCCESS| " dpdklab
2024-03-25 21:42 ` |WARNING| " dpdklab
2024-03-25 21:42 ` |FAILURE| " dpdklab
2024-03-25 21:43 ` |SUCCESS| " dpdklab
2024-03-25 21:43 ` |FAILURE| " dpdklab
2024-03-25 21:43 ` dpdklab
2024-03-25 21:43 ` dpdklab
2024-03-25 21:43 ` dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` |FAILURE| pw138784 [PATCH v12 14/14] maintainers: add for log library 0-day Robot
2024-03-25 21:44 ` |FAILURE| pw138771-138784 [PATCH] [v12,14/14] maintainers: add for l dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` |SUCCESS| " dpdklab
2024-03-25 21:45 ` |FAILURE| " dpdklab
2024-03-25 21:45 ` dpdklab
2024-03-25 21:46 ` |SUCCESS| " dpdklab
2024-03-25 21:46 ` |FAILURE| " dpdklab
2024-03-25 21:46 ` |SUCCESS| " dpdklab
2024-03-25 21:47 ` dpdklab
2024-03-25 21:47 ` |FAILURE| " dpdklab
2024-03-25 21:47 ` |SUCCESS| " dpdklab
2024-03-25 21:47 ` |FAILURE| " dpdklab
2024-03-25 21:48 ` dpdklab
2024-03-25 21:48 ` dpdklab
2024-03-25 21:49 ` dpdklab
2024-03-25 21:49 ` dpdklab
2024-03-25 21:50 ` |SUCCESS| " dpdklab
2024-03-25 21:50 ` dpdklab
2024-03-25 21:51 ` dpdklab
2024-03-25 21:51 ` |FAILURE| " dpdklab
2024-03-25 21:51 ` dpdklab
2024-03-25 21:52 ` dpdklab
2024-03-25 21:53 ` |SUCCESS| " dpdklab
2024-03-25 21:54 ` dpdklab
2024-03-25 21:55 ` |FAILURE| " dpdklab
2024-03-25 22:01 ` dpdklab
2024-03-25 22:07 ` dpdklab
2024-03-25 22:52 ` dpdklab
2024-03-25 23:16 ` |SUCCESS| " dpdklab
2024-03-25 23:56 ` dpdklab
2024-04-01 17:52 ` dpdklab
2024-04-01 17:53 ` dpdklab
2024-04-01 18:10 ` dpdklab
2024-04-01 18:29 ` dpdklab
2024-04-01 18:33 ` 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=202403252038.42PKcSFC2624406@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=stephen@networkplumber.org \
--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).