From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw97700-97703 [PATCH] [4/4] common/qat: add extra data to qat pci dev
Date: Sat, 4 Sep 2021 11:08:20 +0000 (UTC) [thread overview]
Message-ID: <20210904110820.729A16018A@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2796 bytes --]
Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/97703
_Testing PASS_
Submitter: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wednesday, September 01 2021 14:47:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:eeedef704c11bd74c367d62838700bdb8e5b573f
97700-97703 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Ubuntu 18.04 | PASS |
+------------------+----------------+
| Arch Linux | PASS |
+------------------+----------------+
| CentOS 8 | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| Fedora 31 | PASS |
+------------------+----------------+
| Fedora 32 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| RHEL 7 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| Fedora 34 | PASS |
+------------------+----------------+
| Fedora 33 | PASS |
+------------------+----------------+
| Fedora 34 clang | PASS |
+------------------+----------------+
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
CentOS 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18488/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-09-04 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 11:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-04 16:32 dpdklab
2021-09-04 16:30 dpdklab
2021-09-02 0:07 dpdklab
2021-09-01 22:57 dpdklab
2021-09-01 22:36 dpdklab
2021-09-01 21:52 dpdklab
2021-09-01 21:42 dpdklab
2021-09-01 19:44 dpdklab
2021-09-01 19:32 dpdklab
2021-09-01 19:31 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=20210904110820.729A16018A@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@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).