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| pw134557-134561 [PATCH] [5/5] doc: use ordered lists
Date: Thu, 23 Nov 2023 05:37:08 -0800 (PST)	[thread overview]
Message-ID: <655f5584.170a0220.52961.22a9SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Thursday, November 23 2023 11:44:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:202e5b2bf15bbf57090bda4294375d7326fa621b

134557-134561 --> 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/28454/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-23 13:37 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 13:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-23 16:21 dpdklab
2023-11-23 15:33 dpdklab
2023-11-23 15:24 dpdklab
2023-11-23 15:01 dpdklab
2023-11-23 14:49 dpdklab
2023-11-23 14:46 dpdklab
2023-11-23 14:45 dpdklab
2023-11-23 14:45 dpdklab
2023-11-23 14:45 dpdklab
2023-11-23 14:24 dpdklab
2023-11-23 14:23 dpdklab
2023-11-23 14:23 dpdklab
2023-11-23 14:22 dpdklab
2023-11-23 14:22 dpdklab
2023-11-23 14:21 dpdklab
2023-11-23 14:17 dpdklab
2023-11-23 14:17 dpdklab
2023-11-23 14:16 dpdklab
2023-11-23 14:14 dpdklab
2023-11-23 14:13 dpdklab
2023-11-23 14:13 dpdklab
2023-11-23 14:12 dpdklab
2023-11-23 14:11 dpdklab
2023-11-23 14:10 dpdklab
2023-11-23 14:10 dpdklab
2023-11-23 14:10 dpdklab
2023-11-23 14:08 dpdklab
2023-11-23 14:08 dpdklab
2023-11-23 14:07 dpdklab
2023-11-23 14:07 dpdklab
2023-11-23 14:07 dpdklab
2023-11-23 14:07 dpdklab
2023-11-23 14:07 dpdklab
2023-11-23 14:07 dpdklab
2023-11-23 14:07 dpdklab
2023-11-23 14:07 dpdklab
2023-11-23 14:07 dpdklab
2023-11-23 14:06 dpdklab
2023-11-23 14:06 dpdklab
2023-11-23 14:06 dpdklab
2023-11-23 14:06 dpdklab
2023-11-23 14:06 dpdklab
2023-11-23 14:06 dpdklab
2023-11-23 14:03 dpdklab
2023-11-23 14:03 dpdklab
2023-11-23 14:01 dpdklab
2023-11-23 13:58 dpdklab
2023-11-23 13:58 dpdklab
2023-11-23 13:45 dpdklab
2023-11-23 13:42 dpdklab
2023-11-23 13:41 dpdklab
2023-11-23 13:37 dpdklab
2023-11-23 13:37 dpdklab
2023-11-23 13:35 dpdklab
2023-11-23 13:16 dpdklab
     [not found] <20231123114405.2611371-6-david.marchand@redhat.com>
2023-11-23 11:26 ` |SUCCESS| pw134557-134561 [PATCH 5/5] " qemudev
2023-11-23 11:30 ` qemudev

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=655f5584.170a0220.52961.22a9SMTPIN_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).