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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw119987 [PATCH] doc: add tested platforms with NVIDIA NICs
Date: Mon, 21 Nov 2022 04:37:54 -0500 (EST)	[thread overview]
Message-ID: <20221121093754.4A5BF45F@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

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

_Functional Testing PASS_

Submitter: Raslan Darawsheh <rasland@nvidia.com>
Date: Monday, November 21 2022 09:10:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:903ec2b1b49e496815c016b0104fd655cd972661

119987 --> 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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-11-21  9:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21  9:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-21 11:22 dpdklab
2022-11-21 10:44 dpdklab
2022-11-21 10:29 dpdklab
2022-11-21 10:14 dpdklab
2022-11-21 10:12 dpdklab
2022-11-21 10:05 dpdklab
2022-11-21  9:53 dpdklab
2022-11-21  9:52 dpdklab
2022-11-21  9:45 dpdklab
2022-11-21  9:43 dpdklab
     [not found] <20221121091002.18565-1-rasland@nvidia.com>
2022-11-21  9:08 ` qemudev
2022-11-21  9:11 ` checkpatch
2022-11-21  9:12 ` qemudev
2022-11-21 10:21 ` 0-day Robot

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=20221121093754.4A5BF45F@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).