From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: |SUCCESS| pw132266 [PATCH] fib6: fix adding default route as first r
Date: Mon, 02 Oct 2023 09:06:46 -0700 (PDT) [thread overview]
Message-ID: <651aea96.170a0220.3c1da.69c2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132266
_Testing PASS_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Monday, October 02 2023 15:12:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6e999364a6afb9189029154b1ac55b4ad5fb9b3f
132266 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27806/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-02 16:06 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 16:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 17:16 dpdklab
2023-10-02 17:15 dpdklab
2023-10-02 17:10 dpdklab
2023-10-02 17:09 dpdklab
2023-10-02 17:09 dpdklab
2023-10-02 17:07 dpdklab
2023-10-02 17:05 dpdklab
2023-10-02 16:31 dpdklab
2023-10-02 16:24 dpdklab
2023-10-02 16:18 dpdklab
2023-10-02 16:18 dpdklab
2023-10-02 16:13 dpdklab
2023-10-02 16:13 dpdklab
2023-10-02 16:10 dpdklab
2023-10-02 16:08 dpdklab
2023-10-02 16:08 dpdklab
2023-10-02 16:07 dpdklab
2023-10-02 16:06 dpdklab
2023-10-02 16:04 dpdklab
2023-10-02 16:03 dpdklab
2023-10-02 15:56 dpdklab
2023-10-02 15:54 dpdklab
2023-10-02 15:53 dpdklab
2023-10-02 15:53 dpdklab
2023-10-02 15:51 dpdklab
2023-10-02 15:50 dpdklab
2023-10-02 15:50 dpdklab
2023-10-02 15:50 dpdklab
2023-10-02 15:49 dpdklab
2023-10-02 15:48 dpdklab
2023-10-02 15:48 dpdklab
2023-10-02 15:48 dpdklab
2023-10-02 15:48 dpdklab
2023-10-02 15:48 dpdklab
2023-10-02 15:47 dpdklab
2023-10-02 15:47 dpdklab
2023-10-02 15:47 dpdklab
2023-10-02 15:47 dpdklab
2023-10-02 15:46 dpdklab
2023-10-02 15:46 dpdklab
2023-10-02 15:45 dpdklab
2023-10-02 15:45 dpdklab
2023-10-02 15:44 dpdklab
2023-10-02 15:43 dpdklab
2023-10-02 15:43 dpdklab
2023-10-02 15:43 dpdklab
2023-10-02 15:43 dpdklab
2023-10-02 15:43 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=651aea96.170a0220.3c1da.69c2SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=vladimir.medvedkin@intel.com \
/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).