From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137397-137398 [PATCH] [2/2] build: build ring library wi
Date: Tue, 27 Feb 2024 18:16:24 -0800 (PST) [thread overview]
Message-ID: <65de9778.0d0a0220.49eb0.1f2cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709061720-4843-3-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137398
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, February 27 2024 19:22:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137397-137398 --> 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/3
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/29302/
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-02-28 2:16 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1709061720-4843-3-git-send-email-roretzla@linux.microsoft.com>
2024-02-27 18:59 ` |SUCCESS| pw137397-137398 [PATCH 2/2] build: build ring library with MSVC qemudev
2024-02-27 19:03 ` qemudev
2024-02-27 19:23 ` |SUCCESS| pw137398 " checkpatch
2024-02-27 20:25 ` 0-day Robot
2024-02-28 1:41 ` |SUCCESS| pw137397-137398 [PATCH] [2/2] build: build ring library wi dpdklab
2024-02-28 1:59 ` dpdklab
2024-02-28 2:16 ` dpdklab [this message]
2024-02-28 2:22 ` dpdklab
2024-02-28 2:32 ` dpdklab
2024-02-28 2:34 ` dpdklab
2024-02-28 2:35 ` dpdklab
2024-02-28 2:35 ` dpdklab
2024-02-28 2:37 ` dpdklab
2024-02-28 2:38 ` dpdklab
2024-02-28 2:39 ` dpdklab
2024-02-28 2:39 ` dpdklab
2024-02-28 2:39 ` dpdklab
2024-02-28 2:40 ` dpdklab
2024-02-28 2:44 ` dpdklab
2024-02-28 3:11 ` dpdklab
2024-02-28 3:35 ` dpdklab
2024-02-28 3:53 ` dpdklab
2024-02-28 3:53 ` dpdklab
2024-02-28 3:54 ` dpdklab
2024-02-28 3:55 ` dpdklab
2024-02-28 4:02 ` dpdklab
2024-02-28 4:03 ` dpdklab
2024-02-28 4:03 ` dpdklab
2024-02-28 4:03 ` dpdklab
2024-02-28 4:03 ` dpdklab
2024-02-28 4:03 ` dpdklab
2024-02-28 4:04 ` dpdklab
2024-02-28 4:04 ` dpdklab
2024-02-28 4:04 ` dpdklab
2024-02-28 4:04 ` dpdklab
2024-02-28 4:04 ` dpdklab
2024-02-28 4:05 ` dpdklab
2024-02-28 4:05 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:07 ` dpdklab
2024-02-28 4:07 ` dpdklab
2024-02-28 4:08 ` dpdklab
2024-02-28 4:20 ` dpdklab
2024-02-28 4:20 ` dpdklab
2024-02-28 4:21 ` dpdklab
2024-02-28 4:24 ` |FAILURE| " dpdklab
2024-02-28 4:24 ` |SUCCESS| " dpdklab
2024-02-28 4:33 ` dpdklab
2024-02-28 4:40 ` dpdklab
2024-02-28 4:41 ` dpdklab
2024-02-28 4:58 ` dpdklab
2024-02-28 5:14 ` dpdklab
2024-02-28 5:16 ` dpdklab
2024-02-28 5:17 ` dpdklab
2024-02-28 5:28 ` dpdklab
2024-02-28 6:19 ` dpdklab
2024-02-28 6:32 ` dpdklab
2024-02-28 6:44 ` dpdklab
2024-02-28 6:50 ` dpdklab
2024-02-28 6:57 ` dpdklab
2024-02-28 7:33 ` dpdklab
2024-02-28 7:36 ` dpdklab
2024-02-28 7:45 ` dpdklab
2024-02-28 10:38 ` dpdklab
2024-02-28 13:42 ` dpdklab
2024-02-28 13:44 ` dpdklab
2024-02-28 21:46 ` dpdklab
2024-02-29 16:04 ` dpdklab
2024-02-29 16:29 ` dpdklab
2024-02-29 16:35 ` dpdklab
2024-02-29 16:37 ` dpdklab
2024-02-29 16:38 ` dpdklab
2024-02-29 16:45 ` dpdklab
2024-02-29 17:04 ` 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=65de9778.0d0a0220.49eb0.1f2cSMTPIN_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).