From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129211 [PATCH] fib: fix adding a default route
Date: Tue, 11 Jul 2023 22:46:44 -0700 (PDT) [thread overview]
Message-ID: <64ae3e44.0d0a0220.60425.f115SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/129211
_Functional Testing PASS_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Monday, July 03 2023 15:43:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a64a4564705d18d20d20cfa16c79e795b7bf0f1e
129211 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26935/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-12 5:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 5:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 19:45 dpdklab
2023-07-14 19:45 dpdklab
2023-07-12 21:20 dpdklab
2023-07-12 7:19 dpdklab
2023-07-12 5:51 dpdklab
2023-07-12 0:20 dpdklab
2023-07-11 23:09 dpdklab
2023-07-11 23:06 dpdklab
2023-07-11 22:36 dpdklab
2023-07-11 22:02 dpdklab
2023-07-10 22:38 dpdklab
2023-07-10 21:42 dpdklab
2023-07-08 7:17 dpdklab
2023-07-08 6:58 dpdklab
2023-07-06 21:17 dpdklab
2023-07-06 12:06 dpdklab
2023-07-06 9:50 dpdklab
2023-07-06 9:34 dpdklab
2023-07-06 5:06 dpdklab
2023-07-06 5:04 dpdklab
2023-07-06 4:57 dpdklab
2023-07-06 4:57 dpdklab
2023-07-06 4:49 dpdklab
2023-07-06 4:48 dpdklab
2023-07-06 4:45 dpdklab
2023-07-06 4:44 dpdklab
2023-07-06 4:38 dpdklab
2023-07-06 4:38 dpdklab
2023-07-06 4:38 dpdklab
2023-07-06 4:02 dpdklab
2023-07-06 3:40 dpdklab
2023-07-06 3:38 dpdklab
[not found] <20230703154335.69883-1-vladimir.medvedkin@intel.com>
2023-07-03 15:31 ` qemudev
2023-07-03 15:35 ` qemudev
2023-07-03 15:44 ` checkpatch
2023-07-03 16:39 ` 0-day Robot
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=64ae3e44.0d0a0220.60425.f115SMTPIN_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).