From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136132 [PATCH] [v1] doc: update guideline for fix commit
Date: Thu, 25 Jan 2024 05:33:21 -0800 (PST) [thread overview]
Message-ID: <65b26321.020a0220.2db15.1483SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136132
_Functional Testing PASS_
Submitter: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Date: Thursday, January 25 2024 03:39:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2ecc673e5e9a19850ba76d6a976596890f2dade1
136132 --> 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
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
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 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/28962/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-25 13:34 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 13:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 18:36 dpdklab
2024-01-26 18:21 dpdklab
2024-01-25 17:40 dpdklab
2024-01-25 16:17 dpdklab
2024-01-25 16:11 dpdklab
2024-01-25 15:58 dpdklab
2024-01-25 15:32 dpdklab
2024-01-25 15:29 dpdklab
2024-01-25 15:27 dpdklab
2024-01-25 15:18 dpdklab
2024-01-25 15:10 dpdklab
2024-01-25 15:10 dpdklab
2024-01-25 15:10 dpdklab
2024-01-25 15:10 dpdklab
2024-01-25 14:58 dpdklab
2024-01-25 14:58 dpdklab
2024-01-25 14:57 dpdklab
2024-01-25 14:56 dpdklab
2024-01-25 14:55 dpdklab
2024-01-25 14:52 dpdklab
2024-01-25 14:50 dpdklab
2024-01-25 14:49 dpdklab
2024-01-25 14:47 dpdklab
2024-01-25 14:47 dpdklab
2024-01-25 14:45 dpdklab
2024-01-25 14:43 dpdklab
2024-01-25 14:43 dpdklab
2024-01-25 14:38 dpdklab
2024-01-25 14:38 dpdklab
2024-01-25 14:37 dpdklab
2024-01-25 14:37 dpdklab
2024-01-25 14:36 dpdklab
2024-01-25 14:34 dpdklab
2024-01-25 14:32 dpdklab
2024-01-25 14:25 dpdklab
2024-01-25 14:22 dpdklab
2024-01-25 14:18 dpdklab
2024-01-25 14:15 dpdklab
2024-01-25 14:12 dpdklab
2024-01-25 14:11 dpdklab
2024-01-25 14:10 dpdklab
2024-01-25 14:09 dpdklab
2024-01-25 14:07 dpdklab
2024-01-25 13:57 dpdklab
2024-01-25 13:56 dpdklab
2024-01-25 13:51 dpdklab
2024-01-25 13:51 dpdklab
2024-01-25 13:50 dpdklab
2024-01-25 13:35 dpdklab
2024-01-25 13:25 dpdklab
2024-01-25 13:22 dpdklab
2024-01-25 13:20 dpdklab
2024-01-25 13:18 dpdklab
2024-01-25 13:18 dpdklab
2024-01-25 13:16 dpdklab
2024-01-25 13:15 dpdklab
2024-01-25 13:14 dpdklab
2024-01-25 13:13 dpdklab
2024-01-25 13:13 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=65b26321.020a0220.2db15.1483SMTPIN_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).