automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw(103650) sid(20270) job(PER_PATCH_BUILD9438)failsafe: Remove the vdev args check for secondary process which prevents the secondary from attaching to the device created by the primary process via the hotplug framework. This check was removed for other vdevs but was missed for failsafe.
Date: 03 Nov 2021 09:50:52 -0700	[thread overview]
Message-ID: <373a91$dd8usn@orsmga003-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3323 bytes --]


Test-Label: Intel-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/103650

_Compilation OK_

Submitter: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Date: 2021-11-03 12:06:42
Reply_mail: 20211103120642.21976-1-kumaraparamesh92@gmail.com

DPDK git baseline: Repo:dpdk-next-net, CommitID: cabeaec2e6d9c3b5fecdf0068c4714672c15ee65


Meson Build Summary: 20 Builds Done, 20 Successful, 0 Failures, 0 Blocked

+--------------+------------+--------------+------------+------------+-----------+----------+
| os           | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document |
+--------------+------------+--------------+------------+------------+-----------+----------+
| UB2004-64    | pass       | pass         | pass       |            |           | pass     |
| FC34-64      | pass       | pass         |            |            |           |          |
| WIN10-64     |            | pass         |            |            |           |          |
| UB2004-32    | pass       |              |            |            |           |          |
| FreeBSD13-64 | pass       | pass         |            | pass       | pass      |          |
| UB2110-64    | pass       |              |            |            |           |          |
| SUSE15-64    | pass       | pass         |            |            |           |          |
| RHEL84-64    | pass       | pass         | pass       | pass       | pass      |          |
+--------------+------------+--------------+------------+------------+-----------+----------+
Test environment and configuration as below:


OS: UB2004-64
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-icc
	x86_64-native-linuxapp-doc

OS: FC34-64
	Kernel Version: 5.11.15-300.fc34.x86_64
	GCC Version: gcc (GCC) 11.0.1 20210324 (Red Hat 11.0.1-0)
	Clang Version: 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

OS: WIN10-64
	Kernel Version: N/A
	GCC Version: N/A
	Clang Version: Clang 8.0.0
	x86_64-windows-clang

OS: UB2004-32
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
	Clang Version: 10.0.0-4ubuntu1
	i686-native-linuxapp-gcc

OS: FreeBSD13-64
	Kernel Version: 13.0-RELEASE
	GCC Version: gcc (FreeBSD Ports Collection) 10.3.0
	Clang Version: 11.0.1 (git@github.com:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe)
	x86_64-native-bsdapp-gcc
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc+shared
	x86_64-native-bsdapp-gcc+debug

OS: UB2110-64
	Kernel Version: 5.13.0-19-generic
	GCC Version: gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0
	Clang Version: 13.0.0-2
	x86_64-native-linuxapp-gcc

OS: SUSE15-64
	Kernel Version: 5.3.18-57-default
	GCC Version: gcc (SUSE Linux) 7.5.0
	Clang Version: 11.0.1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc

OS: RHEL84-64
	Kernel Version: 4.18.0-305.19.1.el8_4.x86_64
	GCC Version: gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
	Clang Version: 11.0.0 (Red Hat 11.0.0-1.module_el8.4.0+587+5187cac0)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-gcc+debug
	x86_64-native-linuxapp-icc


DPDK STV team

                 reply	other threads:[~2021-11-03 16:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='373a91$dd8usn@orsmga003-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --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).