From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136838-136840 [PATCH] [v2,3/3] testpmd: replace EAL logt
Date: Thu, 15 Feb 2024 20:15:27 -0800 (PST) [thread overview]
Message-ID: <65cee15f.050a0220.5ab93.2798SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136840
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, February 16 2024 03:36:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:62b906cf06ba86adf1f05c16969a9adcc49cf8bc
136838-136840 --> 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/29166/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-16 4:15 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 4:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 5:42 dpdklab
2024-02-16 5:09 dpdklab
2024-02-16 5:09 dpdklab
2024-02-16 4:54 dpdklab
2024-02-16 4:51 dpdklab
2024-02-16 4:51 dpdklab
2024-02-16 4:45 dpdklab
2024-02-16 4:43 dpdklab
2024-02-16 4:43 dpdklab
2024-02-16 4:42 dpdklab
2024-02-16 4:41 dpdklab
2024-02-16 4:40 dpdklab
2024-02-16 4:40 dpdklab
2024-02-16 4:39 dpdklab
2024-02-16 4:39 dpdklab
2024-02-16 4:38 dpdklab
2024-02-16 4:37 dpdklab
2024-02-16 4:35 dpdklab
2024-02-16 4:33 dpdklab
2024-02-16 4:30 dpdklab
2024-02-16 4:30 dpdklab
2024-02-16 4:30 dpdklab
2024-02-16 4:29 dpdklab
2024-02-16 4:29 dpdklab
2024-02-16 4:28 dpdklab
2024-02-16 4:28 dpdklab
2024-02-16 4:28 dpdklab
2024-02-16 4:28 dpdklab
2024-02-16 4:28 dpdklab
2024-02-16 4:27 dpdklab
2024-02-16 4:27 dpdklab
2024-02-16 4:27 dpdklab
2024-02-16 4:26 dpdklab
2024-02-16 4:25 dpdklab
2024-02-16 4:25 dpdklab
2024-02-16 4:24 dpdklab
2024-02-16 4:24 dpdklab
2024-02-16 4:24 dpdklab
2024-02-16 4:23 dpdklab
2024-02-16 4:22 dpdklab
2024-02-16 4:22 dpdklab
2024-02-16 4:22 dpdklab
2024-02-16 4:21 dpdklab
2024-02-16 4:21 dpdklab
2024-02-16 4:20 dpdklab
2024-02-16 4:20 dpdklab
2024-02-16 4:18 dpdklab
2024-02-16 4:17 dpdklab
2024-02-16 4:17 dpdklab
2024-02-16 4:16 dpdklab
2024-02-16 4:16 dpdklab
2024-02-16 4:15 dpdklab
2024-02-16 4:15 dpdklab
2024-02-16 4:15 dpdklab
2024-02-16 4:15 dpdklab
2024-02-16 4:15 dpdklab
2024-02-16 4:15 dpdklab
2024-02-16 4:14 dpdklab
2024-02-16 4:14 dpdklab
2024-02-16 4:13 dpdklab
2024-02-16 4:13 dpdklab
2024-02-16 4:13 dpdklab
2024-02-16 4:13 dpdklab
2024-02-16 4:12 dpdklab
2024-02-16 4:12 dpdklab
2024-02-16 4:12 dpdklab
2024-02-16 4:12 dpdklab
2024-02-16 4:11 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=65cee15f.050a0220.5ab93.2798SMTPIN_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).