automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137455-137454 [PATCH] [v2,3/3] rcu: use rte macro instea
Date: Wed, 28 Feb 2024 11:32:48 -0800 (PST)	[thread overview]
Message-ID: <65df8a60.050a0220.b934f.084fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709146076-22254-4-git-send-email-roretzla@linux.microsoft.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137454

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, February 28 2024 18:47:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137455-137454 --> 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/3


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29321/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-02-28 19:32 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709146076-22254-4-git-send-email-roretzla@linux.microsoft.com>
2024-02-28 18:26 ` |SUCCESS| pw137455-137454 [PATCH v2 3/3] rcu: use rte macro instead of GCC attribute qemudev
2024-02-28 18:30 ` qemudev
2024-02-28 18:49 ` |SUCCESS| pw137454 " checkpatch
2024-02-28 19:24 ` |SUCCESS| pw137455-137454 [PATCH] [v2,3/3] rcu: use rte macro instea dpdklab
2024-02-28 19:25 ` dpdklab
2024-02-28 19:26 ` dpdklab
2024-02-28 19:31 ` dpdklab
2024-02-28 19:32 ` dpdklab
2024-02-28 19:32 ` dpdklab [this message]
2024-02-28 19:37 ` dpdklab
2024-02-28 19:37 ` dpdklab
2024-02-28 19:37 ` dpdklab
2024-02-28 19:37 ` dpdklab
2024-02-28 19:38 ` dpdklab
2024-02-28 19:38 ` dpdklab
2024-02-28 19:38 ` dpdklab
2024-02-28 19:38 ` dpdklab
2024-02-28 19:39 ` dpdklab
2024-02-28 19:39 ` dpdklab
2024-02-28 19:40 ` dpdklab
2024-02-28 19:40 ` dpdklab
2024-02-28 19:40 ` dpdklab
2024-02-28 19:41 ` dpdklab
2024-02-28 19:42 ` dpdklab
2024-02-28 19:43 ` dpdklab
2024-02-28 19:43 ` dpdklab
2024-02-28 19:43 ` dpdklab
2024-02-28 19:45 ` |SUCCESS| pw137454 [PATCH v2 3/3] rcu: use rte macro instead of GCC attribute 0-day Robot
2024-02-28 19:49 ` |SUCCESS| pw137455-137454 [PATCH] [v2,3/3] rcu: use rte macro instea dpdklab
2024-02-28 19:50 ` dpdklab
2024-02-28 19:51 ` dpdklab
2024-02-28 19:51 ` dpdklab
2024-02-28 19:51 ` dpdklab
2024-02-28 19:52 ` dpdklab
2024-02-28 19:52 ` dpdklab
2024-02-28 19:53 ` dpdklab
2024-02-28 19:54 ` dpdklab
2024-02-28 19:55 ` dpdklab
2024-02-28 19:56 ` dpdklab
2024-02-28 19:57 ` dpdklab
2024-02-28 19:58 ` dpdklab
2024-02-28 19:58 ` dpdklab
2024-02-28 19:58 ` dpdklab
2024-02-28 19:59 ` dpdklab
2024-02-28 19:59 ` dpdklab
2024-02-28 19:59 ` dpdklab
2024-02-28 20:00 ` dpdklab
2024-02-28 20:01 ` dpdklab
2024-02-28 20:05 ` dpdklab
2024-02-28 20:05 ` dpdklab
2024-02-28 20:06 ` dpdklab
2024-02-28 20:09 ` dpdklab
2024-02-28 20:10 ` dpdklab
2024-02-28 20:11 ` dpdklab
2024-02-28 20:12 ` dpdklab
2024-02-28 20:15 ` dpdklab
2024-02-28 20:17 ` dpdklab
2024-02-28 20:21 ` dpdklab
2024-02-28 20:28 ` dpdklab
2024-02-28 20:34 ` dpdklab
2024-02-28 20:38 ` dpdklab
2024-02-28 20:52 ` dpdklab
2024-02-28 21:19 ` dpdklab
2024-02-28 22:32 ` dpdklab
2024-02-28 22:39 ` dpdklab
2024-02-28 23:24 ` dpdklab
2024-02-29 20:08 ` dpdklab
2024-03-01  0:36 ` dpdklab
2024-03-01  0:38 ` dpdklab
2024-03-01  0:44 ` dpdklab
2024-03-01  0:46 ` dpdklab
2024-03-02  3:42 ` dpdklab
2024-03-02  4:14 ` dpdklab
2024-03-02  4:47 ` 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=65df8a60.050a0220.b934f.084fSMTPIN_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).