automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw130972 [RFC PATCH] move memset out of hold lock when rte_free
Date: Thu, 31 Aug 2023 19:20:12 +0800	[thread overview]
Message-ID: <202308311120.37VBKCIT1363726@localhost.localdomain> (raw)
In-Reply-To: <20230831111937.60975-1-changfengnan@bytedance.com>

Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130972

_Unit Testing PASS_

Submitter: Fengnan Chang <changfengnan@bytedance.com>
Date: Thu, 31 Aug 2023 19:19:37 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: b7b8de26f34d39c8aaded44d8a468da5e68f19da

130972 --> testing pass

Test environment and result as below:

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

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


Test result details:
 1/92 DPDK:fast-tests / acl_autotest                            OK              3.33s
 2/92 DPDK:fast-tests / atomic_autotest                         OK              7.23s
 3/92 DPDK:fast-tests / bitcount_autotest                       OK              0.47s
 4/92 DPDK:fast-tests / bitmap_autotest                         OK              0.47s
 5/92 DPDK:fast-tests / bitops_autotest                         OK              0.47s
 6/92 DPDK:fast-tests / bpf_autotest                            OK              0.47s
 7/92 DPDK:fast-tests / bpf_convert_autotest                    OK              0.47s
 8/92 DPDK:fast-tests / byteorder_autotest                      OK              0.47s
 9/92 DPDK:fast-tests / cksum_autotest                          OK              0.47s
10/92 DPDK:fast-tests / cmdline_autotest                        OK              0.47s
11/92 DPDK:fast-tests / common_autotest                         OK              1.32s
12/92 DPDK:fast-tests / cpuflags_autotest                       OK              0.47s
13/92 DPDK:fast-tests / crc_autotest                            OK              0.47s
14/92 DPDK:fast-tests / user_delay_us                           OK              0.47s
15/92 DPDK:fast-tests / debug_autotest                          OK             15.36s
16/92 DPDK:fast-tests / devargs_autotest                        OK              0.47s
17/92 DPDK:fast-tests / distributor_autotest                    OK              1.27s
18/92 DPDK:fast-tests / eal_flags_c_opt_autotest                OK              1.22s
19/92 DPDK:fast-tests / eal_flags_main_opt_autotest             OK              0.32s
20/92 DPDK:fast-tests / eal_flags_n_opt_autotest                OK              0.32s
21/92 DPDK:fast-tests / eal_flags_hpet_autotest                 OK              0.17s
22/92 DPDK:fast-tests / eal_flags_no_huge_autotest              OK              0.32s
23/92 DPDK:fast-tests / eal_flags_a_opt_autotest                OK              0.47s
24/92 DPDK:fast-tests / eal_flags_b_opt_autotest                OK              0.37s
25/92 DPDK:fast-tests / eal_flags_vdev_opt_autotest             OK              0.27s
26/92 DPDK:fast-tests / eal_flags_r_opt_autotest                OK              0.27s
27/92 DPDK:fast-tests / eal_flags_mem_autotest                  OK              0.77s
28/92 DPDK:fast-tests / eal_flags_file_prefix_autotest          OK             22.41s
29/92 DPDK:fast-tests / eal_flags_misc_autotest                 OK              1.17s
30/92 DPDK:fast-tests / eal_fs_autotest                         OK              0.47s
31/92 DPDK:fast-tests / errno_autotest                          OK              0.47s
32/92 DPDK:fast-tests / ethdev_link_status                      OK              0.47s
33/92 DPDK:fast-tests / event_ring_autotest                     OK              0.47s
34/92 DPDK:fast-tests / eventdev_common_autotest                OK              0.47s
35/92 DPDK:fast-tests / fbarray_autotest                        OK              0.47s
36/92 DPDK:fast-tests / fib_autotest                            OK              1.12s
37/92 DPDK:fast-tests / fib6_autotest                           OK              1.17s
38/92 DPDK:fast-tests / func_reentrancy_autotest                OK              2.28s
39/92 DPDK:fast-tests / hash_autotest                           OK              1.37s
40/92 DPDK:fast-tests / hash_readwrite_func_autotest            OK              6.49s
41/92 DPDK:fast-tests / interrupt_autotest                      OK              1.77s
42/92 DPDK:fast-tests / ipfrag_autotest                         OK              0.12s
43/92 DPDK:fast-tests / ipsec_autotest                          SKIP            0.47s   exit status 77
44/92 DPDK:fast-tests / kvargs_autotest                         OK              0.47s
45/92 DPDK:fast-tests / lcores_autotest                         OK              5.48s
46/92 DPDK:fast-tests / logs_autotest                           OK              0.47s
47/92 DPDK:fast-tests / lpm_autotest                            OK              2.53s
48/92 DPDK:fast-tests / lpm6_autotest                           OK              5.69s
49/92 DPDK:fast-tests / malloc_autotest                         OK             61.20s
50/92 DPDK:fast-tests / mbuf_autotest                           OK              5.23s
51/92 DPDK:fast-tests / mcslock_autotest                        OK              3.12s
52/92 DPDK:fast-tests / member_autotest                         OK              1.67s
53/92 DPDK:fast-tests / memcpy_autotest                         OK              7.08s
54/92 DPDK:fast-tests / memory_autotest                         OK              0.12s
55/92 DPDK:fast-tests / mempool_autotest                        OK              0.47s
56/92 DPDK:fast-tests / memzone_autotest                        OK              0.17s
57/92 DPDK:fast-tests / meter_autotest                          OK              0.47s
58/92 DPDK:fast-tests / multiprocess_autotest                   OK              0.27s
59/92 DPDK:fast-tests / per_lcore_autotest                      OK              0.57s
60/92 DPDK:fast-tests / pflock_autotest                         OK              1.27s
61/92 DPDK:fast-tests / pie_autotest                            OK              0.47s
62/92 DPDK:fast-tests / power_autotest                          OK              0.47s
63/92 DPDK:fast-tests / power_cpufreq_autotest                  SKIP            0.12s   exit status 77
64/92 DPDK:fast-tests / power_intel_uncore_autotest             SKIP            0.47s   exit status 77
65/92 DPDK:fast-tests / power_kvm_vm_autotest                   SKIP            0.12s   exit status 77
66/92 DPDK:fast-tests / prefetch_autotest                       OK              0.47s
67/92 DPDK:fast-tests / rcu_qsbr_autotest                       OK              0.97s
68/92 DPDK:fast-tests / reorder_autotest                        OK              0.52s
69/92 DPDK:fast-tests / rib_autotest                            OK              9.14s
70/92 DPDK:fast-tests / rib6_autotest                           OK              9.14s
71/92 DPDK:fast-tests / ring_autotest                           OK              0.47s
72/92 DPDK:fast-tests / rwlock_test1_autotest                   OK              1.22s
73/92 DPDK:fast-tests / rwlock_rda_autotest                     OK              5.48s
74/92 DPDK:fast-tests / rwlock_rds_wrm_autotest                 OK              5.68s
75/92 DPDK:fast-tests / rwlock_rde_wro_autotest                 OK              5.48s
76/92 DPDK:fast-tests / sched_autotest                          OK              0.47s
77/92 DPDK:fast-tests / security_autotest                       OK              0.12s
78/92 DPDK:fast-tests / seqlock_autotest                        OK              2.47s
79/92 DPDK:fast-tests / service_autotest                        OK              3.17s
80/92 DPDK:fast-tests / spinlock_autotest                       OK              0.52s
81/92 DPDK:fast-tests / stack_autotest                          OK              0.87s
82/92 DPDK:fast-tests / stack_lf_autotest                       SKIP            0.07s   exit status 77
83/92 DPDK:fast-tests / string_autotest                         OK              0.37s
84/92 DPDK:fast-tests / tailq_autotest                          OK              0.52s
85/92 DPDK:fast-tests / thash_autotest                          OK              0.62s
86/92 DPDK:fast-tests / threads_autotest                        OK              0.82s
87/92 DPDK:fast-tests / ticketlock_autotest                     OK              0.77s
88/92 DPDK:fast-tests / timer_autotest                          OK              3.92s
89/92 DPDK:fast-tests / trace_autotest                          OK              0.32s
90/92 DPDK:fast-tests / trace_autotest_with_traces              OK              0.37s
91/92 DPDK:fast-tests / version_autotest                        OK              0.32s
92/92 DPDK:fast-tests / telemetry_all                           OK              1.27s


Ok:                 87
Expected Fail:      0
Fail:               0
Unexpected Pass:    0
Skipped:            5
Timeout:            0


      parent reply	other threads:[~2023-08-31 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230831111937.60975-1-changfengnan@bytedance.com>
2023-08-31 11:16 ` qemudev
2023-08-31 11:19 ` checkpatch
2023-08-31 11:20 ` qemudev [this message]

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=202308311120.37VBKCIT1363726@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --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).