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| pw142193 [PATCH] [v4] vhost: fix crash caused by accessing
Date: Mon, 08 Jul 2024 01:03:10 -0700 (PDT)	[thread overview]
Message-ID: <668b9d3e.050a0220.6ac28.23d3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <TYAP286MB06491A9489C631C9D6EEA2FFD8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/142193

_Testing PASS_

Submitter: Gongming Chen <chengongming1900@outlook.com>
Date: Monday, July 08 2024 04:41:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9cbdb606e5d04de04be3d9f70f0e76551e8c9a36

142193 --> testing pass

Test environment and result as below:

+---------------------+--------------------+-------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+====================+===================+======================+
| FreeBSD 13.3        | PASS               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-------------------+----------------------+
| FreeBSD 14.1        | PASS               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2022 | PASS               | PASS              | PASS                 |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2019 | PASS               | SKIPPED           | PASS                 |
+---------------------+--------------------+-------------------+----------------------+


FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-08  8:03 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <TYAP286MB06491A9489C631C9D6EEA2FFD8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-07-08  4:15 ` |SUCCESS| pw142193 [PATCH v4] vhost: fix crash caused by accessing a freed vsocket qemudev
2024-07-08  4:19 ` qemudev
2024-07-08  4:43 ` checkpatch
2024-07-08  5:43 ` 0-day Robot
2024-07-08  7:30 ` |SUCCESS| pw142193 [PATCH] [v4] vhost: fix crash caused by accessing dpdklab
2024-07-08  7:30 ` |PENDING| " dpdklab
2024-07-08  7:39 ` |SUCCESS| " dpdklab
2024-07-08  7:43 ` dpdklab
2024-07-08  7:48 ` |PENDING| " dpdklab
2024-07-08  7:50 ` dpdklab
2024-07-08  7:53 ` |SUCCESS| " dpdklab
2024-07-08  7:54 ` |PENDING| " dpdklab
2024-07-08  7:54 ` dpdklab
2024-07-08  7:58 ` dpdklab
2024-07-08  7:59 ` dpdklab
2024-07-08  8:03 ` dpdklab [this message]
2024-07-08  8:12 ` dpdklab
2024-07-08  8:16 ` dpdklab
2024-07-08  8:33 ` |SUCCESS| " dpdklab
2024-07-08  8:50 ` |PENDING| " dpdklab
2024-07-08  9:12 ` dpdklab
2024-07-08  9:25 ` dpdklab
2024-07-08  9:29 ` dpdklab
2024-07-08  9:29 ` dpdklab
2024-07-08  9:32 ` dpdklab
2024-07-08  9:36 ` dpdklab
2024-07-08  9:45 ` dpdklab
2024-07-08  9:46 ` dpdklab
2024-07-08  9:52 ` dpdklab
2024-07-08  9:57 ` dpdklab
2024-07-08 10:00 ` dpdklab
2024-07-08 10:01 ` dpdklab
2024-07-08 10:02 ` dpdklab
2024-07-08 10:05 ` dpdklab
2024-07-08 10:07 ` dpdklab
2024-07-08 10:09 ` dpdklab
2024-07-08 10:12 ` |SUCCESS| " dpdklab
2024-07-08 10:13 ` dpdklab
2024-07-08 10:48 ` dpdklab
2024-07-08 13:08 ` dpdklab
2024-07-08 13:12 ` dpdklab
2024-07-08 13:17 ` dpdklab
2024-07-08 13:27 ` |PENDING| " dpdklab
2024-07-08 13:31 ` dpdklab
2024-07-08 13:32 ` dpdklab
2024-07-08 13:36 ` |SUCCESS| " dpdklab
2024-07-08 13:39 ` |PENDING| " dpdklab
2024-07-08 13:40 ` |SUCCESS| " dpdklab
2024-07-08 13:43 ` |PENDING| " dpdklab
2024-07-08 13:47 ` dpdklab
2024-07-08 13:52 ` dpdklab
2024-07-08 13:55 ` dpdklab
2024-07-08 13:55 ` dpdklab
2024-07-08 14:00 ` dpdklab
2024-07-08 14:00 ` dpdklab
2024-07-08 14:05 ` dpdklab
2024-07-08 14:08 ` dpdklab
2024-07-08 14:08 ` dpdklab
2024-07-08 14:09 ` dpdklab
2024-07-08 14:13 ` dpdklab
2024-07-08 14:13 ` dpdklab
2024-07-08 14:18 ` dpdklab
2024-07-08 14:21 ` dpdklab
2024-07-08 14:25 ` dpdklab
2024-07-08 14:29 ` |SUCCESS| " dpdklab
2024-07-08 14:30 ` |PENDING| " dpdklab
2024-07-08 14:37 ` dpdklab
2024-07-08 14:39 ` dpdklab
2024-07-08 14:42 ` dpdklab
2024-07-08 14:43 ` dpdklab
2024-07-08 14:46 ` dpdklab
2024-07-08 14:46 ` dpdklab
2024-07-08 14:47 ` dpdklab
2024-07-08 14:51 ` dpdklab
2024-07-08 14:54 ` dpdklab
2024-07-08 14:54 ` dpdklab
2024-07-08 14:55 ` dpdklab
2024-07-08 14:59 ` dpdklab
2024-07-08 15:13 ` dpdklab
2024-07-08 15:22 ` dpdklab
2024-07-08 15:34 ` dpdklab
2024-07-09  0:44 ` |SUCCESS| " dpdklab
2024-07-09 15:20 ` dpdklab
2024-07-09 15:33 ` dpdklab
2024-07-13 21:21 ` dpdklab
2024-07-14 10:32 ` dpdklab
2024-07-14 17:02 ` dpdklab
2024-07-15  8:56 ` dpdklab
2024-07-15  9:09 ` 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=668b9d3e.050a0220.6ac28.23d3SMTPIN_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).