From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw(106352) sid(21331) job(PER_PATCH_BUILD876)[v2, 4/4] crypto: modify return value for asym session create
Date: 24 Jan 2022 22:58:18 -0800 [thread overview]
Message-ID: <373a91$e6stso@orsmga003-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3420 bytes --]
Test-Label: Intel-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/106352
_Compilation OK_
Submitter: Power, Ciara <ciara.power@intel.com>
Date: 2022-01-24 15:03:39
Reply_mail: 20220124150339.280090-5-ciara.power@intel.com
DPDK git baseline: Repo:dpdk-next-crypto, CommitID: 93d77b02baad5f52f1b95acc2d0be6e7846d12e8
Meson Build Summary: 20 Builds Done, 20 Successful, 0 Failures, 0 Blocked
+--------------+------------+--------------+------------+------------+-----------+----------+
| os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document |
+--------------+------------+--------------+------------+------------+-----------+----------+
| FC35-64 | pass | pass | | | | |
| FreeBSD13-64 | pass | pass | | pass | pass | |
| RHEL84-64 | pass | pass | pass | pass | pass | |
| SUSE15-64 | pass | pass | | | | |
| UB2004-32 | pass | | | | | |
| UB2004-64 | pass | pass | pass | | | pass |
| UB2110-64 | pass | | | | | |
| RHEL85-64 | pass | | | | | |
+--------------+------------+--------------+------------+------------+-----------+----------+
Test environment and configuration as below:
OS: FC35-64
Kernel Version: 5.14.16-301.fc35.x86_64
GCC Version: gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1)
Clang Version: 13.0.0 (Fedora 13.0.0~rc1-1.fc35)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
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: RHEL84-64
Kernel Version: 4.18.0-348.7.1.el8_5.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)
Clang Version: 12.0.1 (Red Hat 12.0.1-4.module_el8.5.0+1025+93159d6c)
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
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: 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: 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: 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: RHEL85-64
Kernel Version: 4.18.0-348.7.1.el8_5.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)
Clang Version: 12.0.1 (Red Hat 12.0.1-4.module_el8.5.0+1025+93159d6c)
x86_64-native-linuxapp-gcc
DPDK STV team
reply other threads:[~2022-01-25 6:58 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$e6stso@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).