From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw127736-127735 [PATCH] [v4,2/2] test: add reassembly perf
Date: Tue, 30 May 2023 22:38:09 -0700 (PDT) [thread overview]
Message-ID: <6476dd41.810a0220.5a574.dca6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/127735
_Functional Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Wednesday, May 31 2023 04:26:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c9df59bcc9bec67783de98486879594e52bdc418
127736-127735 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26460/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-31 5:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 5:38 dpdklab [this message]
2023-05-31 5:38 dpdklab
2023-05-31 5:42 dpdklab
2023-05-31 5:43 dpdklab
2023-05-31 5:43 dpdklab
2023-05-31 5:49 dpdklab
2023-05-31 5:49 dpdklab
2023-05-31 6:02 dpdklab
2023-05-31 6:58 dpdklab
2023-05-31 7:50 dpdklab
2023-05-31 8:14 dpdklab
2023-05-31 8:36 dpdklab
2023-05-31 9:02 dpdklab
2023-05-31 9:32 dpdklab
2023-06-08 22:22 dpdklab
2023-06-08 22:24 dpdklab
2023-06-08 22:25 dpdklab
2023-06-08 22:25 dpdklab
2023-06-08 22:25 dpdklab
2023-06-08 22:26 dpdklab
2023-06-09 22:50 dpdklab
2023-06-09 22:56 dpdklab
2023-06-09 22:56 dpdklab
2023-06-09 22:56 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=6476dd41.810a0220.5a574.dca6SMTPIN_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).