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| pw131086 [PATCH] maintainers: assign meson.build for drive
Date: Fri, 01 Sep 2023 05:58:41 -0700 (PDT)	[thread overview]
Message-ID: <64f1e001.6b0a0220.15c67.964fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, September 01 2023 12:03:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:62774b78a84e9fa5df56d04cffed69bef8c901f1

131086 --> 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/4


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


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-155-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/27504/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-01 12:58 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 12:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-06  6:47 dpdklab
2023-09-06  6:35 dpdklab
2023-09-06  6:30 dpdklab
2023-09-06  6:25 dpdklab
2023-09-01 13:54 dpdklab
2023-09-01 13:31 dpdklab
2023-09-01 13:20 dpdklab
2023-09-01 13:03 dpdklab
2023-09-01 12:57 dpdklab
2023-09-01 12:55 dpdklab
2023-09-01 12:53 dpdklab
2023-09-01 12:50 dpdklab
2023-09-01 12:47 dpdklab
2023-09-01 12:47 dpdklab
2023-09-01 12:44 dpdklab
2023-09-01 12:43 dpdklab
2023-09-01 12:43 dpdklab
2023-09-01 12:41 dpdklab
2023-09-01 12:40 dpdklab
2023-09-01 12:40 dpdklab
2023-09-01 12:40 dpdklab
2023-09-01 12:39 dpdklab
2023-09-01 12:39 dpdklab
2023-09-01 12:39 dpdklab
2023-09-01 12:38 dpdklab
2023-09-01 12:38 dpdklab
2023-09-01 12:38 dpdklab
2023-09-01 12:38 dpdklab
2023-09-01 12:37 dpdklab
2023-09-01 12:37 dpdklab
2023-09-01 12:37 dpdklab
2023-09-01 12:37 dpdklab
2023-09-01 12:36 dpdklab
2023-09-01 12:36 dpdklab
2023-09-01 12:35 dpdklab
2023-09-01 12:35 dpdklab
2023-09-01 12:34 dpdklab
2023-09-01 12:34 dpdklab
2023-09-01 12:33 dpdklab
2023-09-01 12:33 dpdklab
2023-09-01 12:33 dpdklab
2023-09-01 12:33 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:31 dpdklab
2023-09-01 12:31 dpdklab
2023-09-01 12:31 dpdklab
2023-09-01 12: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=64f1e001.6b0a0220.15c67.964fSMTPIN_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).