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| pw141317 [PATCH] vhost: Fix the crash caused by accessing
Date: Wed, 19 Jun 2024 13:46:08 -0700 (PDT)	[thread overview]
Message-ID: <66734390.050a0220.71356.ab94SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240619083949.72621-1-15957197901@163.com>

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

_Testing PASS_

Submitter: zhaoxinxin <15957197901@163.com>
Date: Wednesday, June 19 2024 08:39:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b303beb6a9b12df49124ee0701027ca72be7aee1

141317 --> 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/30243/

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-19 20:46 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240619083949.72621-1-15957197901@163.com>
2024-06-19  8:16 ` |SUCCESS| pw141317 [PATCH] vhost: Fix the crash caused by accessing the released memory qemudev
2024-06-19  8:21 ` qemudev
2024-06-19  8:44 ` |WARNING| " checkpatch
2024-06-19  9:44 ` |SUCCESS| " 0-day Robot
2024-06-19 15:26 ` |SUCCESS| pw141317 [PATCH] vhost: Fix the crash caused by accessing dpdklab
2024-06-19 15:26 ` dpdklab
2024-06-19 15:27 ` dpdklab
2024-06-19 15:28 ` dpdklab
2024-06-19 15:30 ` dpdklab
2024-06-19 15:30 ` dpdklab
2024-06-19 15:31 ` dpdklab
2024-06-19 15:31 ` dpdklab
2024-06-19 15:32 ` dpdklab
2024-06-19 15:32 ` dpdklab
2024-06-19 15:32 ` dpdklab
2024-06-19 15:33 ` |FAILURE| " dpdklab
2024-06-19 15:33 ` |SUCCESS| " dpdklab
2024-06-19 15:34 ` |FAILURE| " dpdklab
2024-06-19 15:34 ` |SUCCESS| " dpdklab
2024-06-19 15:35 ` dpdklab
2024-06-19 15:36 ` dpdklab
2024-06-19 15:42 ` |FAILURE| " dpdklab
2024-06-19 15:51 ` dpdklab
2024-06-19 16:42 ` |SUCCESS| " dpdklab
2024-06-19 16:44 ` dpdklab
2024-06-19 16:45 ` dpdklab
2024-06-19 16:53 ` dpdklab
2024-06-19 16:55 ` dpdklab
2024-06-19 16:56 ` |FAILURE| " dpdklab
2024-06-19 16:58 ` |SUCCESS| " dpdklab
2024-06-19 16:59 ` dpdklab
2024-06-19 17:01 ` dpdklab
2024-06-19 17:01 ` dpdklab
2024-06-19 17:03 ` dpdklab
2024-06-19 17:06 ` dpdklab
2024-06-19 17:10 ` dpdklab
2024-06-19 17:12 ` dpdklab
2024-06-19 17:12 ` dpdklab
2024-06-19 17:14 ` dpdklab
2024-06-19 17:16 ` dpdklab
2024-06-19 17:19 ` dpdklab
2024-06-19 17:24 ` dpdklab
2024-06-19 17:24 ` dpdklab
2024-06-19 17:29 ` dpdklab
2024-06-19 20:11 ` dpdklab
2024-06-19 20:34 ` dpdklab
2024-06-19 20:35 ` dpdklab
2024-06-19 20:35 ` dpdklab
2024-06-19 20:39 ` dpdklab
2024-06-19 20:39 ` dpdklab
2024-06-19 20:39 ` dpdklab
2024-06-19 20:40 ` dpdklab
2024-06-19 20:43 ` dpdklab
2024-06-19 20:45 ` dpdklab
2024-06-19 20:46 ` dpdklab [this message]
2024-06-19 20:47 ` dpdklab
2024-06-19 20:48 ` dpdklab
2024-06-19 20:49 ` dpdklab
2024-06-19 20:49 ` dpdklab
2024-06-19 20:50 ` dpdklab
2024-06-19 20:50 ` dpdklab
2024-06-19 20:51 ` dpdklab
2024-06-19 20:52 ` dpdklab
2024-06-19 20:53 ` dpdklab
2024-06-19 20:54 ` dpdklab
2024-06-19 20:54 ` dpdklab
2024-06-19 20:57 ` dpdklab
2024-06-19 20:58 ` dpdklab
2024-06-19 20:58 ` dpdklab
2024-06-19 20:59 ` dpdklab
2024-06-19 21:00 ` dpdklab
2024-06-19 21:00 ` dpdklab
2024-06-19 21:03 ` dpdklab
2024-06-19 21:04 ` dpdklab
2024-06-19 21:04 ` dpdklab
2024-06-19 21:05 ` dpdklab
2024-06-19 21:08 ` dpdklab
2024-06-19 21:10 ` dpdklab
2024-06-19 21:13 ` dpdklab
2024-06-19 21:14 ` dpdklab
2024-06-19 21:15 ` dpdklab
2024-06-19 21:18 ` dpdklab
2024-06-19 21:20 ` dpdklab
2024-06-19 21:20 ` dpdklab
2024-06-19 21:25 ` dpdklab
2024-06-19 21:26 ` dpdklab
2024-06-19 21:27 ` dpdklab
2024-06-19 21:28 ` dpdklab
2024-06-19 21:28 ` dpdklab
2024-06-19 21:30 ` dpdklab
2024-06-19 21:31 ` dpdklab
2024-06-19 21:32 ` dpdklab
2024-06-19 21:32 ` dpdklab
2024-06-19 21:32 ` dpdklab
2024-06-19 21:33 ` dpdklab
2024-06-19 21:35 ` dpdklab
2024-06-19 21:36 ` dpdklab
2024-06-19 21:36 ` dpdklab
2024-06-19 21:37 ` dpdklab
2024-06-19 21:43 ` dpdklab
2024-06-19 21:43 ` dpdklab
2024-06-19 21:44 ` dpdklab
2024-06-19 21:44 ` dpdklab
2024-06-19 21:46 ` dpdklab
2024-06-19 21:50 ` dpdklab
2024-06-19 22:06 ` dpdklab
2024-06-19 22:10 ` dpdklab
2024-06-19 22:13 ` dpdklab
2024-06-19 22:17 ` |FAILURE| " dpdklab
2024-06-19 22:20 ` dpdklab
2024-06-19 22:25 ` dpdklab
2024-06-19 22:28 ` dpdklab
2024-06-19 22:32 ` dpdklab
2024-06-19 23:47 ` |SUCCESS| " dpdklab
2024-06-20  4:05 ` dpdklab
2024-06-20  4:30 ` dpdklab
2024-06-21 20:12 ` 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=66734390.050a0220.71356.ab94SMTPIN_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).