automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141277 [PATCH] vhost: Fix the crash caused by accessing
Date: Tue, 18 Jun 2024 15:34:41 -0700 (PDT)	[thread overview]
Message-ID: <66720b81.050a0220.2e322b.54ebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240618055929.40842-1-15957197901@163.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141277

_Testing PASS_

Submitter: zhaoxinxin <15957197901@163.com>
Date: Tuesday, June 18 2024 05:59:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b303beb6a9b12df49124ee0701027ca72be7aee1

141277 --> testing pass

Test environment and result as below:

+-----------------------------+----------------+--------------+
|         Environment         | dpdk_unit_test | lpm_autotest |
+=============================+================+==============+
| 32-bit Ubuntu 20.04.4 (ARM) | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED        | PASS         |
+-----------------------------+----------------+--------------+


32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30226/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-06-18 22:34 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240618055929.40842-1-15957197901@163.com>
2024-06-18 12:39 ` |SUCCESS| pw141277 [PATCH] vhost: Fix the crash caused by accessing the released memory qemudev
2024-06-18 12:43 ` qemudev
2024-06-18 13:07 ` |WARNING| " checkpatch
2024-06-18 18:24 ` |SUCCESS| pw141277 [PATCH] vhost: Fix the crash caused by accessing dpdklab
2024-06-18 18:47 ` dpdklab
2024-06-18 18:51 ` dpdklab
2024-06-18 18:52 ` dpdklab
2024-06-18 18:53 ` dpdklab
2024-06-18 18:54 ` dpdklab
2024-06-18 19:04 ` dpdklab
2024-06-18 19:04 ` |FAILURE| " dpdklab
2024-06-18 19:05 ` |SUCCESS| " dpdklab
2024-06-18 19:13 ` dpdklab
2024-06-18 19:13 ` |FAILURE| " dpdklab
2024-06-18 19:14 ` dpdklab
2024-06-18 19:14 ` |SUCCESS| " dpdklab
2024-06-18 19:17 ` |FAILURE| " dpdklab
2024-06-18 19:17 ` |SUCCESS| " dpdklab
2024-06-18 20:05 ` |FAILURE| " dpdklab
2024-06-18 20:17 ` |SUCCESS| " dpdklab
2024-06-18 20:23 ` dpdklab
2024-06-18 20:23 ` dpdklab
2024-06-18 20:24 ` dpdklab
2024-06-18 20:25 ` dpdklab
2024-06-18 20:26 ` dpdklab
2024-06-18 20:26 ` dpdklab
2024-06-18 20:27 ` dpdklab
2024-06-18 20:27 ` dpdklab
2024-06-18 20:28 ` dpdklab
2024-06-18 21:09 ` dpdklab
2024-06-18 21:28 ` dpdklab
2024-06-18 21:29 ` dpdklab
2024-06-18 21:29 ` dpdklab
2024-06-18 21:29 ` dpdklab
2024-06-18 21:30 ` dpdklab
2024-06-18 21:30 ` dpdklab
2024-06-18 21:31 ` dpdklab
2024-06-18 21:31 ` dpdklab
2024-06-18 21:31 ` dpdklab
2024-06-18 21:32 ` dpdklab
2024-06-18 21:32 ` dpdklab
2024-06-18 21:33 ` dpdklab
2024-06-18 21:35 ` dpdklab
2024-06-18 22:27 ` dpdklab
2024-06-18 22:33 ` dpdklab
2024-06-18 22:34 ` dpdklab [this message]
2024-06-18 22:35 ` dpdklab
2024-06-18 22:35 ` dpdklab
2024-06-18 22:38 ` dpdklab
2024-06-18 22:40 ` dpdklab
2024-06-18 22:42 ` dpdklab
2024-06-18 22:43 ` dpdklab
2024-06-18 22:50 ` dpdklab
2024-06-18 22:59 ` dpdklab
2024-06-18 23:00 ` dpdklab
2024-06-18 23:01 ` dpdklab
2024-06-18 23:03 ` dpdklab
2024-06-18 23:03 ` dpdklab
2024-06-18 23:24 ` dpdklab
2024-06-18 23:24 ` dpdklab
2024-06-18 23:24 ` dpdklab
2024-06-18 23:25 ` dpdklab
2024-06-18 23:26 ` dpdklab
2024-06-18 23:26 ` dpdklab
2024-06-18 23:27 ` dpdklab
2024-06-18 23:27 ` dpdklab
2024-06-18 23:28 ` dpdklab
2024-06-18 23:28 ` dpdklab
2024-06-18 23:28 ` dpdklab
2024-06-18 23:29 ` dpdklab
2024-06-18 23:29 ` dpdklab
2024-06-18 23:31 ` dpdklab
2024-06-18 23:36 ` dpdklab
2024-06-18 23:36 ` dpdklab
2024-06-18 23:37 ` dpdklab
2024-06-18 23:38 ` dpdklab
2024-06-18 23:39 ` dpdklab
2024-06-18 23:39 ` dpdklab
2024-06-18 23:41 ` dpdklab
2024-06-18 23:42 ` dpdklab
2024-06-18 23:42 ` dpdklab
2024-06-18 23:42 ` dpdklab
2024-06-18 23:43 ` dpdklab
2024-06-18 23:43 ` dpdklab
2024-06-18 23:44 ` dpdklab
2024-06-18 23:44 ` dpdklab
2024-06-18 23:46 ` dpdklab
2024-06-18 23:47 ` dpdklab
2024-06-18 23:47 ` dpdklab
2024-06-18 23:49 ` dpdklab
2024-06-18 23:50 ` dpdklab
2024-06-18 23:50 ` dpdklab
2024-06-19  0:12 ` dpdklab
2024-06-19  0:27 ` dpdklab
2024-06-19  0:30 ` dpdklab
2024-06-19  0:30 ` dpdklab
2024-06-19  0:31 ` dpdklab
2024-06-19  0:32 ` dpdklab
2024-06-19  0:34 ` dpdklab
2024-06-19  0:36 ` dpdklab
2024-06-19  0:37 ` dpdklab
2024-06-19  0:37 ` dpdklab
2024-06-19  0:58 ` dpdklab
2024-06-19  1:03 ` dpdklab
2024-06-19  1:05 ` dpdklab
2024-06-19  1:07 ` dpdklab
2024-06-19  1:09 ` dpdklab
2024-06-19  1:09 ` dpdklab
2024-06-19  1:13 ` dpdklab
2024-06-19  1:15 ` dpdklab
2024-06-19  1:19 ` dpdklab
2024-06-19  1:23 ` dpdklab
2024-06-19  1:25 ` dpdklab
2024-06-19  8:46 ` dpdklab
2024-06-19 11:01 ` dpdklab
2024-06-20  4:45 ` 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=66720b81.050a0220.2e322b.54ebSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).