automatic DPDK test reports
 help / color / mirror / Atom feed
* |WARNING| pw127162 [PATCH v2] eal: fix eal init may failed when too much continuous memsegs under legacy mode
       [not found] <20230522124107.99877-1-changfengnan@bytedance.com>
@ 2023-05-22 12:41 ` checkpatch
  2023-05-22 15:40 ` |FAILURE| " 0-day Robot
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 4+ messages in thread
From: checkpatch @ 2023-05-22 12:41 UTC (permalink / raw)
  To: test-report; +Cc: Fengnan Chang

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/127162

_coding style issues_

Must be a reply to the first patch (--in-reply-to).


WARNING:TYPO_SPELLING: 'argment' may be misspelled - perhaps 'argument'?
#87: 
Fix this by add a argment indicate how many pages mapped in

WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#110: 
EAL: Couldn't remap hugepage files into memseg lists

total: 0 errors, 2 warnings, 87 lines checked

^ permalink raw reply	[flat|nested] 4+ messages in thread

* |FAILURE| pw127162 [PATCH v2] eal: fix eal init may failed when too much continuous memsegs under legacy mode
       [not found] <20230522124107.99877-1-changfengnan@bytedance.com>
  2023-05-22 12:41 ` |WARNING| pw127162 [PATCH v2] eal: fix eal init may failed when too much continuous memsegs under legacy mode checkpatch
@ 2023-05-22 15:40 ` 0-day Robot
  2023-05-23 11:19 ` |SUCCESS| " qemudev
  2023-05-23 11:20 ` |FAILURE| " qemudev
  3 siblings, 0 replies; 4+ messages in thread
From: 0-day Robot @ 2023-05-22 15:40 UTC (permalink / raw)
  To: test-report; +Cc: changfengnan, robot

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/127162/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5047435268
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+debug+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
 96/105 DPDK:fast-tests / table_autotest        OK      17.14 s 
 97/105 DPDK:fast-tests / ring_pmd_autotest     OK       0.17 s 
 98/105 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK       1.37 s 
 99/105 DPDK:fast-tests / bitratestats_autotest  OK       0.17 s 
100/105 DPDK:fast-tests / latencystats_autotest  OK       0.17 s 
101/105 DPDK:fast-tests / pdump_autotest        OK       5.24 s 
102/105 DPDK:fast-tests / vdev_autotest         OK       0.17 s 
103/105 DPDK:fast-tests / rawdev_autotest       OK       0.17 s 
104/105 DPDK:fast-tests / compressdev_autotest  SKIP     0.17 s 
105/105 DPDK:fast-tests / telemetry_all         OK       9.40 s 

Ok:                   96
Expected Fail:         0
Fail:                  1
Unexpected Pass:       0
Skipped:               8
Timeout:               0

Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

^ permalink raw reply	[flat|nested] 4+ messages in thread

* |SUCCESS| pw127162 [PATCH v2] eal: fix eal init may failed when too much continuous memsegs under legacy mode
       [not found] <20230522124107.99877-1-changfengnan@bytedance.com>
  2023-05-22 12:41 ` |WARNING| pw127162 [PATCH v2] eal: fix eal init may failed when too much continuous memsegs under legacy mode checkpatch
  2023-05-22 15:40 ` |FAILURE| " 0-day Robot
@ 2023-05-23 11:19 ` qemudev
  2023-05-23 11:20 ` |FAILURE| " qemudev
  3 siblings, 0 replies; 4+ messages in thread
From: qemudev @ 2023-05-23 11:19 UTC (permalink / raw)
  To: test-report

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/127162

_Compilation OK_

Submitter: Fengnan Chang <changfengnan@bytedance.com>
Date: Mon, 22 May 2023 20:41:07 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: a399d7b5a994e335c446d4b15d7622d71dd8848c

127162 --> meson & ninja build successfully

Test environment and result as below:

+---------------------+----------------+
|     Environment     | compilation    |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS           |
+---------------------+----------------+

Loongnix-Server 8.3
    Kernel: 4.19.190+
    Compiler: gcc 8.3


^ permalink raw reply	[flat|nested] 4+ messages in thread

* |FAILURE| pw127162 [PATCH v2] eal: fix eal init may failed when too much continuous memsegs under legacy mode
       [not found] <20230522124107.99877-1-changfengnan@bytedance.com>
                   ` (2 preceding siblings ...)
  2023-05-23 11:19 ` |SUCCESS| " qemudev
@ 2023-05-23 11:20 ` qemudev
  3 siblings, 0 replies; 4+ messages in thread
From: qemudev @ 2023-05-23 11:20 UTC (permalink / raw)
  To: test-report; +Cc: Fengnan Chang, zhoumin

Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/127162

_Unit Testing FAIL_

Submitter: Fengnan Chang <changfengnan@bytedance.com>
Date: Mon, 22 May 2023 20:41:07 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: a399d7b5a994e335c446d4b15d7622d71dd8848c

127162 --> 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/104 DPDK:fast-tests / acl_autotest                            OK              2.78s
  2/104 DPDK:fast-tests / atomic_autotest                         OK              7.08s
  3/104 DPDK:fast-tests / bitmap_autotest                         OK              0.07s
  4/104 DPDK:fast-tests / bpf_autotest                            OK              0.07s
  5/104 DPDK:fast-tests / bpf_convert_autotest                    OK              0.07s
  6/104 DPDK:fast-tests / bitops_autotest                         OK              0.07s
  7/104 DPDK:fast-tests / byteorder_autotest                      OK              0.07s
  8/104 DPDK:fast-tests / cksum_autotest                          OK              0.07s
  9/104 DPDK:fast-tests / cmdline_autotest                        OK              0.07s
 10/104 DPDK:fast-tests / common_autotest                         OK              0.92s
 11/104 DPDK:fast-tests / cpuflags_autotest                       OK              0.07s
 12/104 DPDK:fast-tests / debug_autotest                          OK              0.67s
 13/104 DPDK:fast-tests / devargs_autotest                        OK              0.07s
 14/104 DPDK:fast-tests / eal_flags_c_opt_autotest                OK              0.67s
 15/104 DPDK:fast-tests / eal_flags_main_opt_autotest             OK              0.22s
 16/104 DPDK:fast-tests / eal_flags_n_opt_autotest                OK              0.17s
 17/104 DPDK:fast-tests / eal_flags_hpet_autotest                 OK              0.12s
 18/104 DPDK:fast-tests / eal_flags_no_huge_autotest              OK              0.22s
 19/104 DPDK:fast-tests / eal_flags_a_opt_autotest                OK              0.27s
 20/104 DPDK:fast-tests / eal_flags_b_opt_autotest                OK              0.22s
 21/104 DPDK:fast-tests / eal_flags_vdev_opt_autotest             OK              0.17s
 22/104 DPDK:fast-tests / eal_flags_r_opt_autotest                OK              0.17s
 23/104 DPDK:fast-tests / eal_flags_mem_autotest                  OK              0.52s
 24/104 DPDK:fast-tests / eal_flags_file_prefix_autotest          FAIL           11.09s   exit status 255
 25/104 DPDK:fast-tests / eal_flags_misc_autotest                 OK              0.77s
 26/104 DPDK:fast-tests / eal_fs_autotest                         OK              0.07s
 27/104 DPDK:fast-tests / errno_autotest                          OK              0.07s
 28/104 DPDK:fast-tests / ethdev_link_status                      OK              0.07s
 29/104 DPDK:fast-tests / event_ring_autotest                     OK              0.07s
 30/104 DPDK:fast-tests / fib_autotest                            OK              0.87s
 31/104 DPDK:fast-tests / fib6_autotest                           OK              0.92s
 32/104 DPDK:fast-tests / func_reentrancy_autotest                OK              2.18s
 33/104 DPDK:fast-tests / hash_autotest                           OK              1.02s
 34/104 DPDK:fast-tests / interrupt_autotest                      OK              1.37s
 35/104 DPDK:fast-tests / ipfrag_autotest                         OK              0.07s
 36/104 DPDK:fast-tests / lcores_autotest                         OK              5.12s
 37/104 DPDK:fast-tests / logs_autotest                           OK              0.07s
 38/104 DPDK:fast-tests / lpm_autotest                            OK              5.96s
 39/104 DPDK:fast-tests / lpm6_autotest                           OK              8.82s
 40/104 DPDK:fast-tests / malloc_autotest                         OK             58.81s
 41/104 DPDK:fast-tests / mbuf_autotest                           OK              7.13s
 42/104 DPDK:fast-tests / mcslock_autotest                        OK              3.52s
 43/104 DPDK:fast-tests / memcpy_autotest                         OK              6.68s
 44/104 DPDK:fast-tests / memory_autotest                         OK              0.12s
 45/104 DPDK:fast-tests / mempool_autotest                        OK              0.47s
 46/104 DPDK:fast-tests / memzone_autotest                        OK              0.17s
 47/104 DPDK:fast-tests / meter_autotest                          OK              0.07s
 48/104 DPDK:fast-tests / multiprocess_autotest                   OK              0.17s
 49/104 DPDK:fast-tests / per_lcore_autotest                      OK              0.17s
 50/104 DPDK:fast-tests / pflock_autotest                         OK              0.87s
 51/104 DPDK:fast-tests / prefetch_autotest                       OK              0.07s
 52/104 DPDK:fast-tests / rcu_qsbr_autotest                       OK              0.57s
 53/104 DPDK:fast-tests / pie_autotest                            OK              0.07s
 54/104 DPDK:fast-tests / rib_autotest                            OK             10.30s
 55/104 DPDK:fast-tests / rib6_autotest                           OK             10.30s
 56/104 DPDK:fast-tests / ring_autotest                           OK              0.12s
 57/104 DPDK:fast-tests / rwlock_test1_autotest                   OK              0.82s
 58/104 DPDK:fast-tests / rwlock_rda_autotest                     OK              5.07s
 59/104 DPDK:fast-tests / rwlock_rds_wrm_autotest                 OK              5.07s
 60/104 DPDK:fast-tests / rwlock_rde_wro_autotest                 OK              5.07s
 61/104 DPDK:fast-tests / sched_autotest                          OK              0.07s
 62/104 DPDK:fast-tests / security_autotest                       OK              0.07s
 63/104 DPDK:fast-tests / seqlock_autotest                        OK              2.07s
 64/104 DPDK:fast-tests / spinlock_autotest                       OK              0.17s
 65/104 DPDK:fast-tests / stack_autotest                          OK              0.87s
 66/104 DPDK:fast-tests / stack_lf_autotest                       SKIP            0.07s   exit status 77
 67/104 DPDK:fast-tests / string_autotest                         OK              0.07s
 68/104 DPDK:fast-tests / tailq_autotest                          OK              0.07s
 69/104 DPDK:fast-tests / ticketlock_autotest                     OK              0.22s
 70/104 DPDK:fast-tests / timer_autotest                          OK              3.92s
 71/104 DPDK:fast-tests / user_delay_us                           OK              0.07s
 72/104 DPDK:fast-tests / version_autotest                        OK              0.07s
 73/104 DPDK:fast-tests / crc_autotest                            OK              0.07s
 74/104 DPDK:fast-tests / distributor_autotest                    OK              1.22s
 75/104 DPDK:fast-tests / eventdev_common_autotest                OK              0.07s
 76/104 DPDK:fast-tests / fbarray_autotest                        OK              0.07s
 77/104 DPDK:fast-tests / hash_readwrite_func_autotest            OK              6.39s
 78/104 DPDK:fast-tests / ipsec_autotest                          SKIP            0.07s   exit status 77
 79/104 DPDK:fast-tests / kni_autotest                            SKIP            0.07s   exit status 77
 80/104 DPDK:fast-tests / kvargs_autotest                         OK              0.07s
 81/104 DPDK:fast-tests / member_autotest                         OK              1.22s
 82/104 DPDK:fast-tests / power_cpufreq_autotest                  SKIP            0.07s   exit status 77
 83/104 DPDK:fast-tests / power_autotest                          OK              0.07s
 84/104 DPDK:fast-tests / power_kvm_vm_autotest                   SKIP            0.07s   exit status 77
 85/104 DPDK:fast-tests / power_intel_uncore_autotest             SKIP            0.07s   exit status 77
 86/104 DPDK:fast-tests / reorder_autotest                        OK              0.12s
 87/104 DPDK:fast-tests / service_autotest                        OK              3.02s
 88/104 DPDK:fast-tests / thash_autotest                          OK              0.07s
 89/104 DPDK:fast-tests / threads_autotest                        OK              0.22s
 90/104 DPDK:fast-tests / trace_autotest                          OK              0.07s
 91/104 DPDK:fast-tests / trace_autotest_with_traces              OK              0.12s
 92/104 DPDK:fast-tests / metrics_autotest                        OK              0.07s
 93/104 DPDK:fast-tests / telemetry_json_autotest                 OK              0.07s
 94/104 DPDK:fast-tests / telemetry_data_autotest                 OK              0.07s
 95/104 DPDK:fast-tests / table_autotest                          OK             10.01s
 96/104 DPDK:fast-tests / ring_pmd_autotest                       OK              0.07s
 97/104 DPDK:fast-tests / event_eth_tx_adapter_autotest           OK              1.47s
 98/104 DPDK:fast-tests / bitratestats_autotest                   OK              0.07s
 99/104 DPDK:fast-tests / latencystats_autotest                   OK              0.07s
100/104 DPDK:fast-tests / pdump_autotest                          OK              5.17s
101/104 DPDK:fast-tests / vdev_autotest                           OK              0.07s
102/104 DPDK:fast-tests / rawdev_autotest                         OK              0.07s
103/104 DPDK:fast-tests / compressdev_autotest                    SKIP            0.07s   exit status 77
104/104 DPDK:fast-tests / telemetry_all                           OK             14.79s


Ok:                 96
Expected Fail:      0
Fail:               1
Unexpected Pass:    0
Skipped:            7
Timeout:            0



Test logs for failed test cases:
================================================================================
DPDK:fast-tests / eal_flags_file_prefix_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>eal_flags_file_prefix_autotest
Running binary with argv[]:'/home/zhoumin/dpdk/build/app/test/dpdk-test' '--proc-type=secondary' '-m' '18' '--file-prefix=memtest' 
Running binary with argv[]:'/home/zhoumin/dpdk/build/app/test/dpdk-test' '-m' '18' '--file-prefix=memtest1' 
Running binary with argv[]:'/home/zhoumin/dpdk/build/app/test/dpdk-test' '-m' '18' '--file-prefix=memtest1' '--legacy-mem' 
Error - failed to run with --file-prefix=memtest1
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/eal_flags_file_prefix_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
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/memtest/mp_socket_1332051_3538eb2dc8846
EAL: failed to send to (/var/run/dpdk/memtest/mp_socket) due to No such file or directory
EAL: Fail to send request /var/run/dpdk/memtest/mp_socket:bus_vdev_mp
vdev_scan(): Failed to request vdev from primary
EAL: Selected IOVA mode 'PA'
EAL: Could not map memory from primary process
EAL: It is recommended to disable ASLR in the kernel and retry running both primary and secondary processes
EAL: FATAL: Cannot init memory
EAL: Cannot init memory
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/memtest1/mp_socket
EAL: Selected IOVA mode 'PA'
TELEMETRY: No legacy callbacks, legacy socket not created
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/memtest1/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: Could not find space for memseg. Please increase RTE_MAX_MEMSEG_PER_LIST RTE_MAX_MEMSEG_PER_TYPE and/or RTE_MAX_MEM_MB_PER_TYPE in configuration.
EAL: Couldn't remap hugepage files into memseg lists
EAL: FATAL: Cannot init memory
EAL: Cannot init memory


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-05-23 11:34 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20230522124107.99877-1-changfengnan@bytedance.com>
2023-05-22 12:41 ` |WARNING| pw127162 [PATCH v2] eal: fix eal init may failed when too much continuous memsegs under legacy mode checkpatch
2023-05-22 15:40 ` |FAILURE| " 0-day Robot
2023-05-23 11:19 ` |SUCCESS| " qemudev
2023-05-23 11:20 ` |FAILURE| " qemudev

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).