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| pw137085-137091 [PATCH] [v3,7/7] dts: improve test suite a
Date: Fri, 23 Feb 2024 17:03:52 -0800 (PST)	[thread overview]
Message-ID: <65d94078.810a0220.1a33c.0cc2SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Friday, February 23 2024 07:55:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137085-137091 --> 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 82599ES 10000 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 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/29238/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-24  1:03 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24  1:03 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-24 14:33 dpdklab
2024-02-24 14:05 dpdklab
2024-02-24 13:46 dpdklab
2024-02-24 10:14 dpdklab
2024-02-24  6:03 dpdklab
2024-02-24  4:57 dpdklab
2024-02-24  4:35 dpdklab
2024-02-24  3:57 dpdklab
2024-02-24  3:50 dpdklab
2024-02-24  3:46 dpdklab
2024-02-24  3:46 dpdklab
2024-02-24  3:46 dpdklab
2024-02-24  3:46 dpdklab
2024-02-24  3:46 dpdklab
2024-02-24  3:46 dpdklab
2024-02-24  3:45 dpdklab
2024-02-24  3:45 dpdklab
2024-02-24  3:45 dpdklab
2024-02-24  3:45 dpdklab
2024-02-24  3:45 dpdklab
2024-02-24  3:44 dpdklab
2024-02-24  3:44 dpdklab
2024-02-24  3:44 dpdklab
2024-02-24  3:43 dpdklab
2024-02-24  3:43 dpdklab
2024-02-24  3:43 dpdklab
2024-02-24  3:43 dpdklab
2024-02-24  3:43 dpdklab
2024-02-24  3:42 dpdklab
2024-02-24  3:42 dpdklab
2024-02-24  3:42 dpdklab
2024-02-24  3:37 dpdklab
2024-02-24  3:35 dpdklab
2024-02-24  3:35 dpdklab
2024-02-24  3:35 dpdklab
2024-02-24  3:35 dpdklab
2024-02-24  3:34 dpdklab
2024-02-24  3:34 dpdklab
2024-02-24  3:34 dpdklab
2024-02-24  3:33 dpdklab
2024-02-24  3:33 dpdklab
2024-02-24  3:32 dpdklab
2024-02-24  3:28 dpdklab
2024-02-24  3:26 dpdklab
2024-02-24  3:25 dpdklab
2024-02-24  3:25 dpdklab
2024-02-24  3:24 dpdklab
2024-02-24  3:23 dpdklab
2024-02-24  3:01 dpdklab
2024-02-24  2:21 dpdklab
2024-02-24  2:18 dpdklab
2024-02-24  2:16 dpdklab
2024-02-24  2:14 dpdklab
2024-02-24  2:14 dpdklab
2024-02-24  2:14 dpdklab
2024-02-24  2:14 dpdklab
2024-02-24  2:13 dpdklab
2024-02-24  2:10 dpdklab
2024-02-24  2:07 dpdklab
2024-02-24  2:03 dpdklab
2024-02-24  1:37 dpdklab
2024-02-24  1:36 dpdklab
2024-02-24  1:36 dpdklab
2024-02-24  1:36 dpdklab
2024-02-24  1:34 dpdklab
2024-02-24  1:31 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:16 dpdklab
2024-02-24  1:10 dpdklab
2024-02-24  0:55 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=65d94078.810a0220.1a33c.0cc2SMTPIN_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).