From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130094 [PATCH] graph: mark API's as stable
Date: Thu, 10 Aug 2023 16:51:16 -0700 (PDT) [thread overview]
Message-ID: <64d577f4.9f0a0220.3c257.8537SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130094
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, August 10 2023 18:05:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130094 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Debian Buster | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27287/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-10 23:51 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 23:51 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 3:40 dpdklab
2023-08-14 3:33 dpdklab
2023-08-14 3:30 dpdklab
2023-08-14 3:30 dpdklab
2023-08-14 3:30 dpdklab
2023-08-14 3:29 dpdklab
2023-08-14 3:29 dpdklab
2023-08-14 3:27 dpdklab
2023-08-14 3:27 dpdklab
2023-08-14 3:26 dpdklab
2023-08-14 3:25 dpdklab
2023-08-14 0:07 dpdklab
2023-08-13 19:31 dpdklab
2023-08-11 20:50 dpdklab
2023-08-11 18:37 dpdklab
2023-08-11 18:33 dpdklab
2023-08-11 18:17 dpdklab
2023-08-11 18:12 dpdklab
2023-08-11 13:41 dpdklab
2023-08-11 6:25 dpdklab
2023-08-11 0:30 dpdklab
2023-08-10 23:57 dpdklab
2023-08-10 23:57 dpdklab
2023-08-10 23:55 dpdklab
2023-08-10 23:53 dpdklab
2023-08-10 23:49 dpdklab
2023-08-10 23:48 dpdklab
2023-08-10 23:47 dpdklab
2023-08-10 23:45 dpdklab
2023-08-10 23:44 dpdklab
2023-08-10 23:43 dpdklab
2023-08-10 23:33 dpdklab
2023-08-10 23:21 dpdklab
2023-08-10 23:10 dpdklab
2023-08-10 23:10 dpdklab
2023-08-10 23:09 dpdklab
2023-08-10 23:09 dpdklab
2023-08-10 23:08 dpdklab
2023-08-10 23:08 dpdklab
2023-08-10 23:08 dpdklab
2023-08-10 23:07 dpdklab
2023-08-10 23:05 dpdklab
2023-08-10 22:56 dpdklab
[not found] <20230810180515.113700-1-stephen@networkplumber.org>
2023-08-10 18:06 ` checkpatch
2023-08-10 18:58 ` 0-day Robot
2023-08-10 22:53 ` qemudev
2023-08-10 22:57 ` qemudev
2023-08-10 22:48 dpdklab
2023-08-10 22:48 dpdklab
2023-08-10 22:46 dpdklab
2023-08-10 22:46 dpdklab
2023-08-10 22:44 dpdklab
2023-08-10 22:44 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:40 dpdklab
2023-08-10 22:40 dpdklab
2023-08-10 22:39 dpdklab
2023-08-10 21:46 dpdklab
2023-08-10 21:42 dpdklab
2023-08-10 20:39 dpdklab
2023-08-10 20:38 dpdklab
2023-08-10 20:33 dpdklab
2023-08-10 20:30 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=64d577f4.9f0a0220.3c257.8537SMTPIN_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).