From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138577 [PATCH] graph: enhance export to graphviz
Date: Wed, 20 Mar 2024 11:48:13 -0700 (PDT) [thread overview]
Message-ID: <65fb2f6d.050a0220.291e8.f991SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240320171120.255142-2-rjarry@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138577
_Functional Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Wednesday, March 20 2024 17:11:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138577 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
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/29606/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-20 18:48 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320171120.255142-2-rjarry@redhat.com>
2024-03-20 16:50 ` qemudev
2024-03-20 16:54 ` qemudev
2024-03-20 17:12 ` checkpatch
2024-03-20 18:04 ` |FAILURE| " 0-day Robot
2024-03-20 18:38 ` |SUCCESS| " dpdklab
2024-03-20 18:42 ` dpdklab
2024-03-20 18:44 ` dpdklab
2024-03-20 18:44 ` dpdklab
2024-03-20 18:44 ` dpdklab
2024-03-20 18:44 ` dpdklab
2024-03-20 18:45 ` dpdklab
2024-03-20 18:45 ` dpdklab
2024-03-20 18:46 ` dpdklab
2024-03-20 18:46 ` dpdklab
2024-03-20 18:47 ` dpdklab
2024-03-20 18:47 ` dpdklab
2024-03-20 18:48 ` dpdklab
2024-03-20 18:48 ` dpdklab [this message]
2024-03-20 18:48 ` dpdklab
2024-03-20 18:48 ` dpdklab
2024-03-20 18:48 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-20 18:51 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:58 ` dpdklab
2024-03-20 18:59 ` dpdklab
2024-03-20 18:59 ` dpdklab
2024-03-20 19:00 ` dpdklab
2024-03-20 19:01 ` dpdklab
2024-03-20 19:15 ` dpdklab
2024-03-20 19:15 ` dpdklab
2024-03-20 19:16 ` dpdklab
2024-03-20 19:17 ` dpdklab
2024-03-20 19:18 ` dpdklab
2024-03-20 19:30 ` dpdklab
2024-03-20 19:36 ` dpdklab
2024-03-20 20:09 ` dpdklab
2024-03-21 13:25 ` dpdklab
2024-03-22 7:11 ` dpdklab
2024-03-22 7:50 ` 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=65fb2f6d.050a0220.291e8.f991SMTPIN_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).