From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126155 [PATCH] [v3, 1/4] doc: announce new cpu flag added to rte_cpu_flag_t
Date: Mon, 17 Apr 2023 11:34:17 +0000 (UTC) [thread overview]
Message-ID: <20230417113417.7686860092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126155
_Testing PASS_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Monday, April 17 2023 04:31:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126155 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| Debian Buster | PASS |
+-----------------+----------+
| RHEL 7 | PASS |
+-----------------+----------+
| Debian Bullseye | PASS |
+-----------------+----------+
| CentOS Stream 9 | PASS |
+-----------------+----------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26011/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-17 11:34 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 11:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-17 13:07 dpdklab
2023-04-17 13:06 dpdklab
2023-04-17 12:49 dpdklab
2023-04-17 12:29 dpdklab
2023-04-17 12:21 dpdklab
2023-04-17 12:17 dpdklab
2023-04-17 12:07 dpdklab
2023-04-17 12:06 dpdklab
2023-04-17 12:01 dpdklab
2023-04-17 11:57 dpdklab
2023-04-17 11:56 dpdklab
2023-04-17 11:52 dpdklab
2023-04-17 11:52 dpdklab
2023-04-17 11:39 dpdklab
2023-04-17 11:35 dpdklab
2023-04-17 11:35 dpdklab
2023-04-17 11:31 dpdklab
2023-04-17 11:30 dpdklab
2023-04-17 11:30 dpdklab
2023-04-17 11:21 dpdklab
2023-04-17 11:15 dpdklab
2023-04-17 10:54 dpdklab
2023-04-17 10:45 dpdklab
2023-04-17 10:45 dpdklab
2023-04-17 10:45 dpdklab
2023-04-17 10:41 dpdklab
2023-04-17 10:38 dpdklab
2023-04-17 10:37 dpdklab
2023-04-17 10:29 dpdklab
2023-04-17 10:27 dpdklab
2023-04-17 10:26 dpdklab
2023-04-17 10:25 dpdklab
2023-04-17 10:24 dpdklab
2023-04-17 10:24 dpdklab
2023-04-17 10:22 dpdklab
2023-04-17 10:21 dpdklab
2023-04-17 10:20 dpdklab
2023-04-17 10:19 dpdklab
2023-04-17 10:18 dpdklab
2023-04-17 10:12 dpdklab
2023-04-17 10:10 dpdklab
2023-04-17 10:09 dpdklab
2023-04-17 10:09 dpdklab
2023-04-17 10:06 dpdklab
2023-04-17 10:04 dpdklab
2023-04-17 10:03 dpdklab
2023-04-17 10:01 dpdklab
2023-04-17 10:01 dpdklab
2023-04-17 10:00 dpdklab
2023-04-17 9:59 dpdklab
2023-04-17 9:56 dpdklab
2023-04-17 9:55 dpdklab
2023-04-17 9:55 dpdklab
2023-04-17 9:53 dpdklab
2023-04-17 9:53 dpdklab
2023-04-17 9:48 dpdklab
2023-04-17 9:45 dpdklab
[not found] <20230417043136.470110-1-sivaprasad.tummala@amd.com>
2023-04-17 4:32 ` |SUCCESS| pw126155 [PATCH v3 " checkpatch
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=20230417113417.7686860092@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).