From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142199-142206 [PATCH] [v3,8/8] mempool/dpaax: cache free
Date: Mon, 08 Jul 2024 09:29:35 -0700 (PDT) [thread overview]
Message-ID: <668c13ef.050a0220.b1ea4.1099SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240708072945.2376209-9-vanshika.shukla@nxp.com>
Test-Label: iol-abi-testing
Test-Status: PENDING
http://dpdk.org/patch/142206
_Testing pending_
Submitter: None <vanshika.shukla@nxp.com>
Date: Monday, July 08 2024 07:29:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:90c38f8182246d4f8039db59882b11f6bbf88d1b
142199-142206 --> testing pending
Test environment and result as below:
+-------------------+----------+
| Environment | abi_test |
+===================+==========+
| CentOS Stream 8 | PASS |
+-------------------+----------+
| CentOS Stream 9 | PASS |
+-------------------+----------+
| Fedora 37 | PASS |
+-------------------+----------+
| Debian 12 | PEND |
+-------------------+----------+
| Fedora 39 (Clang) | PASS |
+-------------------+----------+
| Fedora 38 | PEND |
+-------------------+----------+
| Debian Bullseye | PASS |
+-------------------+----------+
| Fedora 38 (Clang) | PASS |
+-------------------+----------+
| Fedora 39 | PEND |
+-------------------+----------+
| Fedora 40 (Clang) | PASS |
+-------------------+----------+
| Fedora 40 | PEND |
+-------------------+----------+
| openSUSE Leap 15 | PEND |
+-------------------+----------+
| RHEL8 | PEND |
+-------------------+----------+
| RHEL9 | PEND |
+-------------------+----------+
| Ubuntu 22.04 | PEND |
+-------------------+----------+
| Ubuntu 24.04 | PEND |
+-------------------+----------+
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.1.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30452/
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-07-08 16:29 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240708072945.2376209-9-vanshika.shukla@nxp.com>
2024-07-08 7:04 ` |SUCCESS| pw142199-142206 [PATCH v3 8/8] mempool/dpaax: cache free optimization qemudev
2024-07-08 7:09 ` qemudev
2024-07-08 7:32 ` |SUCCESS| pw142206 " checkpatch
2024-07-08 8:23 ` 0-day Robot
2024-07-08 12:13 ` |PENDING| pw142199-142206 [PATCH] [v3,8/8] mempool/dpaax: cache free dpdklab
2024-07-08 12:18 ` dpdklab
2024-07-08 12:21 ` |SUCCESS| " dpdklab
2024-07-08 12:26 ` |PENDING| " dpdklab
2024-07-08 12:27 ` dpdklab
2024-07-08 12:28 ` dpdklab
2024-07-08 12:31 ` dpdklab
2024-07-08 12:31 ` dpdklab
2024-07-08 12:31 ` |SUCCESS| " dpdklab
2024-07-08 12:32 ` |PENDING| " dpdklab
2024-07-08 12:34 ` |SUCCESS| " dpdklab
2024-07-08 12:35 ` dpdklab
2024-07-08 12:39 ` dpdklab
2024-07-08 12:44 ` |PENDING| " dpdklab
2024-07-08 12:47 ` dpdklab
2024-07-08 12:47 ` dpdklab
2024-07-08 12:54 ` |SUCCESS| " dpdklab
2024-07-08 13:02 ` |PENDING| " dpdklab
2024-07-08 13:28 ` |SUCCESS| " dpdklab
2024-07-08 14:57 ` dpdklab
2024-07-08 15:02 ` dpdklab
2024-07-08 15:06 ` dpdklab
2024-07-08 15:11 ` dpdklab
2024-07-08 15:29 ` dpdklab
2024-07-08 15:58 ` |PENDING| " dpdklab
2024-07-08 16:01 ` dpdklab
2024-07-08 16:22 ` dpdklab
2024-07-08 16:23 ` dpdklab
2024-07-08 16:25 ` dpdklab
2024-07-08 16:26 ` dpdklab
2024-07-08 16:28 ` dpdklab
2024-07-08 16:29 ` dpdklab [this message]
2024-07-08 16:33 ` dpdklab
2024-07-08 16:33 ` dpdklab
2024-07-08 16:33 ` dpdklab
2024-07-08 16:34 ` dpdklab
2024-07-08 16:35 ` dpdklab
2024-07-08 16:37 ` dpdklab
2024-07-08 16:38 ` dpdklab
2024-07-08 16:39 ` dpdklab
2024-07-08 16:41 ` dpdklab
2024-07-08 16:41 ` dpdklab
2024-07-08 16:41 ` dpdklab
2024-07-08 16:42 ` dpdklab
2024-07-08 16:42 ` dpdklab
2024-07-08 16:44 ` dpdklab
2024-07-08 16:48 ` dpdklab
2024-07-08 16:50 ` dpdklab
2024-07-08 16:52 ` dpdklab
2024-07-08 16:52 ` dpdklab
2024-07-08 16:52 ` dpdklab
2024-07-08 16:54 ` dpdklab
2024-07-08 16:54 ` |SUCCESS| " dpdklab
2024-07-08 16:54 ` |PENDING| " dpdklab
2024-07-08 16:58 ` dpdklab
2024-07-08 16:58 ` dpdklab
2024-07-08 16:59 ` dpdklab
2024-07-08 16:59 ` dpdklab
2024-07-08 17:03 ` dpdklab
2024-07-08 17:05 ` dpdklab
2024-07-08 17:06 ` dpdklab
2024-07-08 17:06 ` dpdklab
2024-07-08 17:07 ` dpdklab
2024-07-08 17:07 ` dpdklab
2024-07-08 17:09 ` dpdklab
2024-07-08 17:10 ` dpdklab
2024-07-08 17:10 ` dpdklab
2024-07-08 17:13 ` dpdklab
2024-07-08 17:13 ` dpdklab
2024-07-08 17:24 ` dpdklab
2024-07-08 17:25 ` |FAILURE| " dpdklab
2024-07-08 17:27 ` |PENDING| " dpdklab
2024-07-08 17:28 ` |SUCCESS| " dpdklab
2024-07-08 17:44 ` dpdklab
2024-07-08 17:48 ` |FAILURE| " dpdklab
2024-07-08 17:48 ` dpdklab
2024-07-08 17:50 ` dpdklab
2024-07-09 13:54 ` |SUCCESS| " dpdklab
2024-07-09 17:12 ` dpdklab
2024-07-13 20:33 ` dpdklab
2024-07-14 10:15 ` dpdklab
2024-07-14 16:48 ` dpdklab
2024-07-15 8:31 ` dpdklab
2024-07-15 8:38 ` 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=668c13ef.050a0220.b1ea4.1099SMTPIN_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).