From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138331 [PATCH] app/crypto-perf-test: fix unset crc algor
Date: Wed, 13 Mar 2024 08:56:33 -0700 (PDT) [thread overview]
Message-ID: <65f1ccb1.170a0220.546d8.0845SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240313145448.26264-1-arkadiuszx.kusztal@intel.com>
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138331
_Testing PASS_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wednesday, March 13 2024 14:54:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:197bb4582c43df3c40db97a0da463afea5e74951
138331 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian 12 (arm) | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29535/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-13 15:56 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240313145448.26264-1-arkadiuszx.kusztal@intel.com>
2024-03-13 14:34 ` |SUCCESS| pw138331 [PATCH] app/crypto-perf-test: fix unset crc algorithm qemudev
2024-03-13 14:38 ` qemudev
2024-03-13 14:55 ` checkpatch
2024-03-13 15:38 ` |SUCCESS| pw138331 [PATCH] app/crypto-perf-test: fix unset crc algor dpdklab
2024-03-13 15:39 ` dpdklab
2024-03-13 15:39 ` dpdklab
2024-03-13 15:39 ` dpdklab
2024-03-13 15:39 ` dpdklab
2024-03-13 15:40 ` dpdklab
2024-03-13 15:40 ` dpdklab
2024-03-13 15:40 ` dpdklab
2024-03-13 15:40 ` dpdklab
2024-03-13 15:41 ` dpdklab
2024-03-13 15:41 ` dpdklab
2024-03-13 15:41 ` dpdklab
2024-03-13 15:42 ` dpdklab
2024-03-13 15:42 ` dpdklab
2024-03-13 15:42 ` dpdklab
2024-03-13 15:43 ` dpdklab
2024-03-13 15:43 ` dpdklab
2024-03-13 15:43 ` dpdklab
2024-03-13 15:43 ` |SUCCESS| pw138331 [PATCH] app/crypto-perf-test: fix unset crc algorithm 0-day Robot
2024-03-13 15:43 ` |SUCCESS| pw138331 [PATCH] app/crypto-perf-test: fix unset crc algor dpdklab
2024-03-13 15:44 ` dpdklab
2024-03-13 15:44 ` dpdklab
2024-03-13 15:45 ` dpdklab
2024-03-13 15:45 ` dpdklab
2024-03-13 15:45 ` dpdklab
2024-03-13 15:45 ` dpdklab
2024-03-13 15:46 ` dpdklab
2024-03-13 15:46 ` dpdklab
2024-03-13 15:46 ` dpdklab
2024-03-13 15:47 ` dpdklab
2024-03-13 15:47 ` dpdklab
2024-03-13 15:47 ` dpdklab
2024-03-13 15:47 ` dpdklab
2024-03-13 15:48 ` |FAILURE| " dpdklab
2024-03-13 15:48 ` |SUCCESS| " dpdklab
2024-03-13 15:48 ` |FAILURE| " dpdklab
2024-03-13 15:48 ` |SUCCESS| " dpdklab
2024-03-13 15:49 ` |FAILURE| " dpdklab
2024-03-13 15:49 ` |SUCCESS| " dpdklab
2024-03-13 15:49 ` dpdklab
2024-03-13 15:49 ` dpdklab
2024-03-13 15:49 ` dpdklab
2024-03-13 15:50 ` dpdklab
2024-03-13 15:50 ` |FAILURE| " dpdklab
2024-03-13 15:50 ` dpdklab
2024-03-13 15:51 ` |SUCCESS| " dpdklab
2024-03-13 15:51 ` dpdklab
2024-03-13 15:51 ` |FAILURE| " dpdklab
2024-03-13 15:51 ` |SUCCESS| " dpdklab
2024-03-13 15:51 ` dpdklab
2024-03-13 15:52 ` dpdklab
2024-03-13 15:52 ` |FAILURE| " dpdklab
2024-03-13 15:52 ` |SUCCESS| " dpdklab
2024-03-13 15:52 ` dpdklab
2024-03-13 15:52 ` dpdklab
2024-03-13 15:53 ` |FAILURE| " dpdklab
2024-03-13 15:53 ` dpdklab
2024-03-13 15:53 ` |SUCCESS| " dpdklab
2024-03-13 15:53 ` dpdklab
2024-03-13 15:53 ` dpdklab
2024-03-13 15:53 ` |FAILURE| " dpdklab
2024-03-13 15:53 ` |SUCCESS| " dpdklab
2024-03-13 15:54 ` |FAILURE| " dpdklab
2024-03-13 15:55 ` dpdklab
2024-03-13 15:55 ` |SUCCESS| " dpdklab
2024-03-13 15:56 ` dpdklab [this message]
2024-03-13 15:57 ` dpdklab
2024-03-13 15:57 ` dpdklab
2024-03-13 16:01 ` dpdklab
2024-03-13 16:04 ` dpdklab
2024-03-13 16:04 ` |FAILURE| " dpdklab
2024-03-13 16:04 ` |SUCCESS| " dpdklab
2024-03-13 16:05 ` dpdklab
2024-03-13 17:05 ` dpdklab
2024-03-17 5:23 ` dpdklab
2024-03-17 5:52 ` 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=65f1ccb1.170a0220.546d8.0845SMTPIN_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).