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| pw139068 [PATCH] vhost: fix crash caused by accessing a fr
Date: Wed, 03 Apr 2024 02:00:30 -0700 (PDT)	[thread overview]
Message-ID: <660d1aae.050a0220.299e5.1c89SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <TYAP286MB0649D9A112E62A15C4792253D83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>

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

_Testing PASS_

Submitter: Gongming Chen <chengongming1900@outlook.com>
Date: Wednesday, April 03 2024 06:31:00 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:deedfb86a7a6e10064d3cccd593f62072de96e36

139068 --> testing pass

Test environment and result as below:

+---------------------+----------------------+--------------------+-------------------+
|     Environment     | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+======================+====================+===================+
| Windows Server 2019 | PASS                 | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Windows Server 2022 | PASS                 | PASS               | PASS              |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 13.2        | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| CentOS Stream 8     | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Debian Bullseye     | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Fedora 38           | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| CentOS Stream 9     | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Fedora 37           | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Fedora 39           | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| openSUSE Leap 15    | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Debian 12           | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| RHEL8               | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Ubuntu 22.04        | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Ubuntu 20.04        | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Alpine              | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+


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

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

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 14.0.5

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Alpine
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-03  9:00 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <TYAP286MB0649D9A112E62A15C4792253D83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-04-03  6:07 ` |SUCCESS| pw139068 [PATCH] vhost: fix crash caused by accessing a freed vsocket qemudev
2024-04-03  6:12 ` qemudev
2024-04-03  6:33 ` checkpatch
2024-04-03  7:26 ` 0-day Robot
2024-04-03  7:30 ` |SUCCESS| pw139068 [PATCH] vhost: fix crash caused by accessing a fr dpdklab
2024-04-03  7:31 ` dpdklab
2024-04-03  7:32 ` dpdklab
2024-04-03  7:34 ` dpdklab
2024-04-03  7:34 ` dpdklab
2024-04-03  8:23 ` dpdklab
2024-04-03  8:25 ` dpdklab
2024-04-03  8:26 ` dpdklab
2024-04-03  8:27 ` dpdklab
2024-04-03  8:29 ` dpdklab
2024-04-03  8:29 ` dpdklab
2024-04-03  8:30 ` dpdklab
2024-04-03  8:31 ` dpdklab
2024-04-03  8:32 ` dpdklab
2024-04-03  8:34 ` dpdklab
2024-04-03  8:35 ` dpdklab
2024-04-03  8:36 ` dpdklab
2024-04-03  8:37 ` dpdklab
2024-04-03  8:37 ` dpdklab
2024-04-03  8:37 ` dpdklab
2024-04-03  8:38 ` dpdklab
2024-04-03  8:38 ` dpdklab
2024-04-03  8:38 ` dpdklab
2024-04-03  8:39 ` dpdklab
2024-04-03  8:40 ` dpdklab
2024-04-03  8:52 ` dpdklab
2024-04-03  8:52 ` dpdklab
2024-04-03  8:53 ` dpdklab
2024-04-03  8:53 ` dpdklab
2024-04-03  8:53 ` dpdklab
2024-04-03  8:54 ` dpdklab
2024-04-03  8:55 ` dpdklab
2024-04-03  8:56 ` dpdklab
2024-04-03  8:56 ` dpdklab
2024-04-03  8:56 ` dpdklab
2024-04-03  8:57 ` dpdklab
2024-04-03  8:58 ` dpdklab
2024-04-03  8:58 ` dpdklab
2024-04-03  8:58 ` dpdklab
2024-04-03  8:58 ` dpdklab
2024-04-03  9:00 ` dpdklab
2024-04-03  9:00 ` dpdklab [this message]
2024-04-03  9:00 ` dpdklab
2024-04-03  9:00 ` dpdklab
2024-04-03  9:01 ` dpdklab
2024-04-03  9:01 ` dpdklab
2024-04-03  9:01 ` dpdklab
2024-04-03  9:01 ` dpdklab
2024-04-03  9:02 ` dpdklab
2024-04-03  9:02 ` dpdklab
2024-04-03  9:02 ` dpdklab
2024-04-03  9:11 ` dpdklab
2024-04-03  9:14 ` dpdklab
2024-04-03  9:16 ` dpdklab
2024-04-03  9:17 ` dpdklab
2024-04-03  9:17 ` dpdklab
2024-04-03  9:18 ` dpdklab
2024-04-03  9:18 ` dpdklab
2024-04-03  9:19 ` dpdklab
2024-04-03  9:20 ` dpdklab
2024-04-03  9:20 ` dpdklab
2024-04-03  9:21 ` dpdklab
2024-04-03  9:22 ` dpdklab
2024-04-03  9:22 ` dpdklab
2024-04-03  9:22 ` dpdklab
2024-04-03  9:23 ` dpdklab
2024-04-03  9:23 ` dpdklab
2024-04-03  9:24 ` dpdklab
2024-04-03  9:24 ` dpdklab
2024-04-03  9:25 ` dpdklab
2024-04-03  9:27 ` dpdklab
2024-04-03  9:27 ` dpdklab
2024-04-03  9:28 ` dpdklab
2024-04-03  9:30 ` dpdklab
2024-04-03  9:30 ` dpdklab
2024-04-03  9:31 ` dpdklab
2024-04-03  9:32 ` dpdklab
2024-04-03  9:42 ` dpdklab
2024-04-03 10:16 ` dpdklab
2024-04-03 10:52 ` dpdklab
2024-04-03 11:29 ` dpdklab
2024-04-03 11:34 ` dpdklab
2024-04-03 12:02 ` dpdklab
2024-04-03 12:39 ` dpdklab
2024-04-04  3:31 ` dpdklab
2024-04-04  3:38 ` dpdklab
2024-04-04  3:43 ` dpdklab
2024-04-04  3:48 ` dpdklab
2024-04-04  3:53 ` 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=660d1aae.050a0220.299e5.1c89SMTPIN_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).