From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132263 [PATCH] doc/contributing: update test guidelines
Date: Mon, 02 Oct 2023 10:15:40 -0700 (PDT) [thread overview]
Message-ID: <651afabc.020a0220.6a97.3f30SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/132263
_Functional Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, October 02 2023 12:44:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6e999364a6afb9189029154b1ac55b4ad5fb9b3f
132263 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27803/
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 17:15 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 17:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 22:10 dpdklab
2023-10-02 18:42 dpdklab
2023-10-02 18:29 dpdklab
2023-10-02 18:28 dpdklab
2023-10-02 18:28 dpdklab
2023-10-02 18:27 dpdklab
2023-10-02 18:26 dpdklab
2023-10-02 18:18 dpdklab
2023-10-02 18:12 dpdklab
2023-10-02 18:12 dpdklab
2023-10-02 18:09 dpdklab
2023-10-02 18:09 dpdklab
2023-10-02 18:05 dpdklab
2023-10-02 18:01 dpdklab
2023-10-02 17:39 dpdklab
2023-10-02 17:29 dpdklab
2023-10-02 17:26 dpdklab
2023-10-02 17:25 dpdklab
2023-10-02 17:23 dpdklab
2023-10-02 17:19 dpdklab
2023-10-02 17:17 dpdklab
2023-10-02 17:17 dpdklab
2023-10-02 17:17 dpdklab
2023-10-02 17:17 dpdklab
2023-10-02 17:17 dpdklab
2023-10-02 17:17 dpdklab
2023-10-02 17:17 dpdklab
2023-10-02 17:16 dpdklab
2023-10-02 17:16 dpdklab
2023-10-02 17:16 dpdklab
2023-10-02 17:16 dpdklab
2023-10-02 17:15 dpdklab
2023-10-02 17:15 dpdklab
2023-10-02 17:15 dpdklab
2023-10-02 17:15 dpdklab
2023-10-02 17:14 dpdklab
2023-10-02 17:14 dpdklab
2023-10-02 17:14 dpdklab
2023-10-02 17:14 dpdklab
2023-10-02 17:14 dpdklab
2023-10-02 17:14 dpdklab
2023-10-02 17:14 dpdklab
2023-10-02 17:13 dpdklab
2023-10-02 17:13 dpdklab
2023-10-02 17:13 dpdklab
2023-10-02 17:13 dpdklab
2023-10-02 17:11 dpdklab
2023-10-02 17:08 dpdklab
2023-10-02 17:05 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=651afabc.020a0220.6a97.3f30SMTPIN_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).