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,
	Gongming Chen <chengongming1900@outlook.com>
Subject: |FAILURE| pw139067 [PATCH] vhost: fix crash caused by accessing a fr
Date: Wed, 03 Apr 2024 02:25:29 -0700 (PDT)	[thread overview]
Message-ID: <660d2089.b00a0220.179ca.b3c3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <TYAP286MB0649A160A9852720E0F3D67BD83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/139067

_Testing issues_

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

139067 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| FreeBSD 13.2        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Debian Bullseye     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Debian 12           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 37           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 38           | FAIL               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 39           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 8     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+

==== 20 line log output for Fedora 38 (dpdk_meson_compile): ====
../lib/vhost/vhost_thread.c:15:1: error: mutex 'vhost_thread_lock' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
../lib/vhost/vhost_thread.c:14:2: note: mutex acquired here
rte_rwlock_read_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:20:2: error: releasing mutex 'vhost_thread_lock' that was not held [-Werror,-Wthread-safety-analysis]
rte_rwlock_read_unlock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:27:1: error: mutex 'vhost_thread_lock' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
../lib/vhost/vhost_thread.c:26:2: note: mutex acquired here
rte_rwlock_write_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:32:2: error: releasing mutex 'vhost_thread_lock' that was not held [-Werror,-Wthread-safety-analysis]
rte_rwlock_write_unlock(&vhost_thread_lock);
^
4 errors generated.
ninja: build stopped: subcommand failed.
==== End log output ====

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 14.0.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)

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

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

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

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

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

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

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <TYAP286MB0649A160A9852720E0F3D67BD83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-04-03  3:03 ` |SUCCESS| pw139067 [PATCH] vhost: fix crash caused by accessing a freed vsocket qemudev
2024-04-03  3:27 ` checkpatch
2024-04-03  4:25 ` |FAILURE| " 0-day Robot
2024-04-03  8:22 ` |SUCCESS| pw139067 [PATCH] vhost: fix crash caused by accessing a fr dpdklab
2024-04-03  8:24 ` dpdklab
2024-04-03  8:27 ` dpdklab
2024-04-03  8:33 ` dpdklab
2024-04-03  8:33 ` dpdklab
2024-04-03  8:39 ` 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: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:57 ` dpdklab
2024-04-03  8:57 ` dpdklab
2024-04-03  8:58 ` dpdklab
2024-04-03  8:58 ` dpdklab
2024-04-03  8:59 ` dpdklab
2024-04-03  9:15 ` |FAILURE| " dpdklab
2024-04-03  9:16 ` dpdklab
2024-04-03  9:17 ` dpdklab
2024-04-03  9:18 ` dpdklab
2024-04-03  9:19 ` dpdklab
2024-04-03  9:19 ` dpdklab
2024-04-03  9:20 ` |SUCCESS| " dpdklab
2024-04-03  9:22 ` |FAILURE| " 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:24 ` dpdklab
2024-04-03  9:25 ` dpdklab [this message]
2024-04-03  9:25 ` dpdklab
2024-04-03  9:25 ` dpdklab
2024-04-03  9:26 ` dpdklab
2024-04-03  9:26 ` dpdklab
2024-04-03  9:26 ` dpdklab
2024-04-03  9:27 ` dpdklab
2024-04-03  9:27 ` dpdklab
2024-04-03  9:27 ` dpdklab
2024-04-03  9:27 ` dpdklab
2024-04-03  9:28 ` dpdklab
2024-04-03  9:28 ` dpdklab
2024-04-03  9:28 ` dpdklab
2024-04-03  9:28 ` dpdklab
2024-04-03  9:28 ` dpdklab
2024-04-03  9:28 ` |SUCCESS| " dpdklab
2024-04-03  9:29 ` |FAILURE| " dpdklab
2024-04-03  9:29 ` dpdklab
2024-04-03  9:29 ` dpdklab
2024-04-03  9:30 ` dpdklab
2024-04-03  9:30 ` |SUCCESS| " dpdklab
2024-04-03  9:30 ` |FAILURE| " dpdklab
2024-04-03  9:31 ` dpdklab
2024-04-03  9:31 ` dpdklab
2024-04-03  9:32 ` dpdklab
2024-04-03  9:32 ` dpdklab
2024-04-03  9:32 ` dpdklab
2024-04-03  9:33 ` dpdklab
2024-04-03  9:34 ` dpdklab
2024-04-03  9:35 ` dpdklab
2024-04-03  9:36 ` |SUCCESS| " dpdklab
2024-04-03  9:37 ` dpdklab
2024-04-03  9:37 ` |FAILURE| " dpdklab
2024-04-03  9:38 ` dpdklab
2024-04-03  9:39 ` dpdklab
2024-04-03  9:40 ` dpdklab
2024-04-03  9:40 ` dpdklab
2024-04-03  9:42 ` dpdklab
2024-04-03  9:44 ` dpdklab
2024-04-03  9:44 ` dpdklab
2024-04-03  9:45 ` dpdklab
2024-04-03  9:46 ` dpdklab
2024-04-03  9:52 ` dpdklab
2024-04-03  9:52 ` dpdklab
2024-04-03 10:11 ` dpdklab
2024-04-03 11:01 ` dpdklab
2024-04-03 11:03 ` dpdklab
2024-04-03 11:18 ` |SUCCESS| " dpdklab
2024-04-03 13:08 ` |FAILURE| " dpdklab
2024-04-03 13:35 ` |SUCCESS| " dpdklab
2024-04-03 13:55 ` dpdklab
2024-04-04  4:00 ` dpdklab
2024-04-04  4:30 ` dpdklab
2024-04-04  5:13 ` dpdklab
2024-04-04  5:56 ` dpdklab
2024-04-04  6:01 ` dpdklab
2024-04-07  1:11 ` |SUCCESS| pw139067 [PATCH] vhost: fix crash caused by accessing a freed vsocket qemudev

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=660d2089.b00a0220.179ca.b3c3SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=chengongming1900@outlook.com \
    --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).