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| pw122478 [PATCH] [v2] mailmap: update contributor entry
Date: Tue, 24 Jan 2023 15:18:02 -0500 (EST)	[thread overview]
Message-ID: <20230124201802.B5E8245F@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Functional Testing PASS_

Submitter: Viacheslav Galaktionov <Viacheslav.Galaktionov@arknetworks.am>
Date: Tuesday, January 24 2023 13:01:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2a211079a92e962bbd0ec81e425a6ffc32890e67

122478 --> 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/2


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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/25066/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-01-24 20:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 20:18 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-25 13:09 dpdklab
2023-01-25  1:23 dpdklab
2023-01-25  1:02 dpdklab
2023-01-24 23:33 dpdklab
2023-01-24 22:14 dpdklab
2023-01-24 22:03 dpdklab
2023-01-24 21:13 dpdklab
2023-01-24 21:12 dpdklab
2023-01-24 21:12 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 20:33 dpdklab
2023-01-24 19:36 dpdklab
2023-01-24 14:12 dpdklab
     [not found] <20230124130110.19666-1-viacheslav.galaktionov@arknetworks.am>
2023-01-24 13:59 ` |SUCCESS| pw122478 [PATCH v2] " 0-day Robot
2023-01-25  1:45 ` qemudev
2023-01-25  1:49 ` qemudev
2023-01-24 13:31 |SUCCESS| pw122478 [PATCH] [v2] " dpdklab
2023-01-24 13:31 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=20230124201802.B5E8245F@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).