From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130520-130518 [PATCH] [v3,8/8] net/ntnic: adds socket co
Date: Fri, 18 Aug 2023 08:41:02 -0700 (PDT) [thread overview]
Message-ID: <64df910e.170a0220.dc197.40b0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130518
_Testing PASS_
Submitter: Mykola Kostenok <mko-plv@napatech.com>
Date: Friday, August 18 2023 10:56:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130520-130518 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27383/
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-18 15:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 15:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-19 5:42 dpdklab
2023-08-19 2:45 dpdklab
2023-08-19 1:46 dpdklab
2023-08-19 1:42 dpdklab
2023-08-19 1:09 dpdklab
2023-08-18 17:17 dpdklab
2023-08-18 16:47 dpdklab
2023-08-18 16:39 dpdklab
2023-08-18 16:22 dpdklab
2023-08-18 16:16 dpdklab
2023-08-18 16:15 dpdklab
2023-08-18 16:14 dpdklab
2023-08-18 16:11 dpdklab
2023-08-18 16:08 dpdklab
2023-08-18 16:00 dpdklab
2023-08-18 15:58 dpdklab
2023-08-18 15:58 dpdklab
2023-08-18 15:57 dpdklab
2023-08-18 15:54 dpdklab
2023-08-18 15:54 dpdklab
2023-08-18 15:46 dpdklab
2023-08-18 15:44 dpdklab
2023-08-18 15:42 dpdklab
2023-08-18 15:42 dpdklab
2023-08-18 15:41 dpdklab
2023-08-18 15:40 dpdklab
2023-08-18 15:36 dpdklab
2023-08-18 15:33 dpdklab
2023-08-18 15:24 dpdklab
2023-08-18 15:04 dpdklab
2023-08-18 15:03 dpdklab
2023-08-18 15:02 dpdklab
2023-08-18 15:02 dpdklab
2023-08-18 15:01 dpdklab
2023-08-18 14:58 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=64df910e.170a0220.dc197.40b0SMTPIN_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).