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| pw141207 [PATCH] vhost: Fix the crash caused by accessing
Date: Mon, 17 Jun 2024 20:55:16 -0700 (PDT)	[thread overview]
Message-ID: <66710524.170a0220.b9429.b9baSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240617033539.36949-1-15957197901@163.com>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141207

_Testing PASS_

Submitter: zhaoxinxin <15957197901@163.com>
Date: Monday, June 17 2024 03:35:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b303beb6a9b12df49124ee0701027ca72be7aee1

141207 --> testing pass

Test environment and result as below:

+----------------------+--------------------+
|     Environment      | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS               |
+----------------------+--------------------+
| Debian 12 with MUSDK | PASS               |
+----------------------+--------------------+
| RHEL9 (ARM)          | PASS               |
+----------------------+--------------------+
| Fedora 40 (ARM)      | PASS               |
+----------------------+--------------------+


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

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

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

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  3:55 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240617033539.36949-1-15957197901@163.com>
2024-06-17 13:51 ` |SUCCESS| pw141207 [PATCH] vhost: Fix the crash caused by accessing the released memory qemudev
2024-06-17 13:56 ` qemudev
2024-06-17 14:15 ` |WARNING| " checkpatch
2024-06-18  0:55 ` |SUCCESS| pw141207 [PATCH] vhost: Fix the crash caused by accessing dpdklab
2024-06-18  1:23 ` dpdklab
2024-06-18  1:26 ` dpdklab
2024-06-18  1:30 ` dpdklab
2024-06-18  1:33 ` dpdklab
2024-06-18  1:37 ` |FAILURE| " dpdklab
2024-06-18  1:38 ` |SUCCESS| " dpdklab
2024-06-18  1:38 ` dpdklab
2024-06-18  2:03 ` |FAILURE| " dpdklab
2024-06-18  2:17 ` |SUCCESS| " dpdklab
2024-06-18  2:18 ` dpdklab
2024-06-18  2:18 ` dpdklab
2024-06-18  2:19 ` |FAILURE| " dpdklab
2024-06-18  2:25 ` dpdklab
2024-06-18  2:28 ` |SUCCESS| " dpdklab
2024-06-18  2:28 ` dpdklab
2024-06-18  2:28 ` dpdklab
2024-06-18  2:28 ` dpdklab
2024-06-18  2:30 ` |FAILURE| " dpdklab
2024-06-18  2:32 ` |SUCCESS| " dpdklab
2024-06-18  2:41 ` dpdklab
2024-06-18  2:53 ` dpdklab
2024-06-18  2:54 ` dpdklab
2024-06-18  2:58 ` dpdklab
2024-06-18  3:00 ` dpdklab
2024-06-18  3:04 ` dpdklab
2024-06-18  3:06 ` dpdklab
2024-06-18  3:11 ` dpdklab
2024-06-18  3:12 ` dpdklab
2024-06-18  3:12 ` dpdklab
2024-06-18  3:16 ` dpdklab
2024-06-18  3:22 ` dpdklab
2024-06-18  3:35 ` dpdklab
2024-06-18  3:36 ` dpdklab
2024-06-18  3:38 ` dpdklab
2024-06-18  3:41 ` dpdklab
2024-06-18  3:46 ` dpdklab
2024-06-18  3:47 ` dpdklab
2024-06-18  3:53 ` dpdklab
2024-06-18  3:53 ` dpdklab
2024-06-18  3:54 ` dpdklab
2024-06-18  3:55 ` dpdklab [this message]
2024-06-18  3:56 ` dpdklab
2024-06-18  3:56 ` dpdklab
2024-06-18  3:57 ` dpdklab
2024-06-18  3:58 ` dpdklab
2024-06-18  3:58 ` dpdklab
2024-06-18  3:59 ` dpdklab
2024-06-18  3:59 ` dpdklab
2024-06-18  4:00 ` dpdklab
2024-06-18  4:00 ` dpdklab
2024-06-18  4:01 ` dpdklab
2024-06-18  4:02 ` dpdklab
2024-06-18  4:04 ` dpdklab
2024-06-18  4:06 ` dpdklab
2024-06-18  4:09 ` dpdklab
2024-06-18  4:12 ` dpdklab
2024-06-18  4:23 ` dpdklab
2024-06-18  4:24 ` dpdklab
2024-06-18  4:25 ` dpdklab
2024-06-18  4:25 ` dpdklab
2024-06-18  4:25 ` dpdklab
2024-06-18  4:28 ` dpdklab
2024-06-18  4:31 ` dpdklab
2024-06-18  4:31 ` dpdklab
2024-06-18  4:36 ` dpdklab
2024-06-18  4:36 ` dpdklab
2024-06-18  4:37 ` dpdklab
2024-06-18  4:38 ` dpdklab
2024-06-18  4:38 ` dpdklab
2024-06-18  4:38 ` dpdklab
2024-06-18  4:38 ` dpdklab
2024-06-18  4:38 ` dpdklab
2024-06-18  4:39 ` dpdklab
2024-06-18  4:39 ` dpdklab
2024-06-18  4:39 ` dpdklab
2024-06-18  4:39 ` dpdklab
2024-06-18  4:39 ` dpdklab
2024-06-18  4:39 ` dpdklab
2024-06-18  4:40 ` dpdklab
2024-06-18  4:40 ` dpdklab
2024-06-18  4:40 ` dpdklab
2024-06-18  4:41 ` dpdklab
2024-06-18  4:41 ` dpdklab
2024-06-18  4:41 ` dpdklab
2024-06-18  4:41 ` dpdklab
2024-06-18  4:42 ` dpdklab
2024-06-18  4:42 ` dpdklab
2024-06-18  4:42 ` dpdklab
2024-06-18  4:42 ` dpdklab
2024-06-18  4:42 ` dpdklab
2024-06-18  4:43 ` dpdklab
2024-06-18  4:44 ` dpdklab
2024-06-18  4:44 ` dpdklab
2024-06-18  4:44 ` dpdklab
2024-06-18  5:18 ` dpdklab
2024-06-18  5:19 ` dpdklab
2024-06-18  5:21 ` dpdklab
2024-06-18  5:23 ` dpdklab
2024-06-18  5:24 ` dpdklab
2024-06-18  5:29 ` dpdklab
2024-06-18  5:29 ` dpdklab
2024-06-18  5:30 ` dpdklab
2024-06-18  5:44 ` dpdklab
2024-06-18  5:44 ` dpdklab
2024-06-18  5:45 ` dpdklab
2024-06-18  5:46 ` dpdklab
2024-06-18  7:21 ` dpdklab
2024-06-18  7:28 ` dpdklab
2024-06-18  7:31 ` dpdklab
2024-06-18  9:14 ` dpdklab
2024-06-18 10:39 ` dpdklab
2024-06-18 14:58 ` 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=66710524.170a0220.b9429.b9baSMTPIN_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).