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| pw137092 [PATCH] [v1] dts: fix smoke tests driver regex
Date: Fri, 23 Feb 2024 16:39:33 -0800 (PST)	[thread overview]
Message-ID: <65d93ac5.020a0220.9fb24.005eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

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

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


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

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  0:39 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24  0:39 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-24 13:23 dpdklab
2024-02-24 12:55 dpdklab
2024-02-24 12:36 dpdklab
2024-02-24  9:11 dpdklab
2024-02-24  5:23 dpdklab
2024-02-24  4:02 dpdklab
2024-02-24  3:33 dpdklab
2024-02-24  3:32 dpdklab
2024-02-24  3:26 dpdklab
2024-02-24  3:20 dpdklab
2024-02-24  3:19 dpdklab
2024-02-24  3:19 dpdklab
2024-02-24  3:19 dpdklab
2024-02-24  3:18 dpdklab
2024-02-24  3:09 dpdklab
2024-02-24  3:09 dpdklab
2024-02-24  3:03 dpdklab
2024-02-24  3:00 dpdklab
2024-02-24  3:00 dpdklab
2024-02-24  3:00 dpdklab
2024-02-24  2:59 dpdklab
2024-02-24  2:58 dpdklab
2024-02-24  2:58 dpdklab
2024-02-24  2:58 dpdklab
2024-02-24  2:57 dpdklab
2024-02-24  2:57 dpdklab
2024-02-24  2:57 dpdklab
2024-02-24  2:54 dpdklab
2024-02-24  2:53 dpdklab
2024-02-24  2:53 dpdklab
2024-02-24  2:52 dpdklab
2024-02-24  2:52 dpdklab
2024-02-24  2:51 dpdklab
2024-02-24  2:51 dpdklab
2024-02-24  2:51 dpdklab
2024-02-24  2:51 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:49 dpdklab
2024-02-24  2:49 dpdklab
2024-02-24  2:49 dpdklab
2024-02-24  2:49 dpdklab
2024-02-24  2:46 dpdklab
2024-02-24  2:41 dpdklab
2024-02-24  2:36 dpdklab
2024-02-24  1:36 dpdklab
2024-02-24  1:35 dpdklab
2024-02-24  1:34 dpdklab
2024-02-24  1:34 dpdklab
2024-02-24  1:33 dpdklab
2024-02-24  1:19 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:16 dpdklab
2024-02-24  1:16 dpdklab
2024-02-24  1:15 dpdklab
2024-02-24  1:04 dpdklab
2024-02-24  1:04 dpdklab
2024-02-24  1:04 dpdklab
2024-02-24  1:04 dpdklab
2024-02-24  0:54 dpdklab
2024-02-24  0:52 dpdklab
2024-02-24  0:48 dpdklab
2024-02-24  0:34 dpdklab
     [not found] <20240223083001.63167-1-juraj.linkes@pantheon.tech>
2024-02-23  8:07 ` |SUCCESS| pw137092 [PATCH v1] " qemudev
2024-02-23  8:11 ` qemudev
2024-02-23  8:30 ` checkpatch
2024-02-23  9:25 ` 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=65d93ac5.020a0220.9fb24.005eSMTPIN_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).