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| pw142302-142319 [PATCH] [v6,21/21] net/ntnic: add physical
Date: Thu, 11 Jul 2024 12:36:08 -0700 (PDT)	[thread overview]
Message-ID: <66903428.050a0220.b131.fb10SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240711120737.698176-21-sil-plv@napatech.com>

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142319

_Functional Testing PASS_

Submitter: Serhii Iliushyk <sil-plv@napatech.com>
Date: Thursday, July 11 2024 12:07:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a6c3ec342ee105e322ffdb21e810cdfd38455c62

142302-142319 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| scatter         |  PASS  |
+-----------------+--------+
| unit_tests_mbuf |  PASS  |
+-----------------+--------+


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-11 19:36 UTC|newest]

Thread overview: 119+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240711120737.698176-21-sil-plv@napatech.com>
2024-07-11 11:57 ` |SUCCESS| pw142302-142319 [PATCH v6 21/21] net/ntnic: add physical layer control module qemudev
2024-07-11 12:02 ` qemudev
2024-07-11 12:11 ` |SUCCESS| pw142319 " checkpatch
2024-07-11 13:03 ` 0-day Robot
2024-07-11 17:17 ` |SUCCESS| pw142302-142319 [PATCH] [v6,21/21] net/ntnic: add physical dpdklab
2024-07-11 17:22 ` dpdklab
2024-07-11 17:23 ` dpdklab
2024-07-11 17:28 ` dpdklab
2024-07-11 17:30 ` dpdklab
2024-07-11 17:37 ` dpdklab
2024-07-11 17:44 ` dpdklab
2024-07-11 17:44 ` dpdklab
2024-07-11 18:28 ` |PENDING| " dpdklab
2024-07-11 18:30 ` dpdklab
2024-07-11 18:41 ` dpdklab
2024-07-11 18:43 ` dpdklab
2024-07-11 18:50 ` dpdklab
2024-07-11 18:50 ` dpdklab
2024-07-11 18:51 ` dpdklab
2024-07-11 18:52 ` dpdklab
2024-07-11 18:53 ` dpdklab
2024-07-11 18:56 ` dpdklab
2024-07-11 18:57 ` dpdklab
2024-07-11 18:58 ` dpdklab
2024-07-11 18:58 ` |SUCCESS| " dpdklab
2024-07-11 19:00 ` |PENDING| " dpdklab
2024-07-11 19:01 ` dpdklab
2024-07-11 19:01 ` dpdklab
2024-07-11 19:04 ` |SUCCESS| " dpdklab
2024-07-11 19:04 ` dpdklab
2024-07-11 19:06 ` |PENDING| " dpdklab
2024-07-11 19:06 ` |SUCCESS| " dpdklab
2024-07-11 19:09 ` |PENDING| " dpdklab
2024-07-11 19:11 ` dpdklab
2024-07-11 19:12 ` |SUCCESS| " dpdklab
2024-07-11 19:13 ` dpdklab
2024-07-11 19:13 ` dpdklab
2024-07-11 19:14 ` dpdklab
2024-07-11 19:18 ` |PENDING| " dpdklab
2024-07-11 19:18 ` dpdklab
2024-07-11 19:29 ` |WARNING| " dpdklab
2024-07-11 19:29 ` dpdklab
2024-07-11 19:31 ` dpdklab
2024-07-11 19:33 ` |FAILURE| " dpdklab
2024-07-11 19:33 ` |SUCCESS| " dpdklab
2024-07-11 19:35 ` |FAILURE| " dpdklab
2024-07-11 19:36 ` dpdklab [this message]
2024-07-11 19:38 ` dpdklab
2024-07-11 19:39 ` dpdklab
2024-07-11 19:40 ` |SUCCESS| " dpdklab
2024-07-11 19:41 ` |FAILURE| " dpdklab
2024-07-11 19:44 ` dpdklab
2024-07-11 19:45 ` |SUCCESS| " dpdklab
2024-07-11 19:46 ` |FAILURE| " dpdklab
2024-07-11 19:53 ` dpdklab
2024-07-11 19:56 ` dpdklab
2024-07-11 20:03 ` dpdklab
2024-07-11 20:03 ` dpdklab
2024-07-11 20:05 ` |WARNING| " dpdklab
2024-07-11 20:05 ` |SUCCESS| " dpdklab
2024-07-11 21:07 ` |PENDING| " dpdklab
2024-07-11 21:08 ` dpdklab
2024-07-11 21:11 ` dpdklab
2024-07-11 21:14 ` dpdklab
2024-07-11 21:15 ` dpdklab
2024-07-11 21:17 ` |WARNING| " dpdklab
2024-07-11 21:26 ` |PENDING| " dpdklab
2024-07-11 21:28 ` dpdklab
2024-07-11 21:28 ` dpdklab
2024-07-11 21:29 ` dpdklab
2024-07-11 21:36 ` dpdklab
2024-07-11 21:39 ` dpdklab
2024-07-11 21:40 ` dpdklab
2024-07-11 21:47 ` dpdklab
2024-07-11 21:48 ` dpdklab
2024-07-11 21:49 ` dpdklab
2024-07-11 21:49 ` dpdklab
2024-07-11 21:52 ` dpdklab
2024-07-11 21:55 ` dpdklab
2024-07-11 21:55 ` dpdklab
2024-07-11 21:58 ` |SUCCESS| " dpdklab
2024-07-11 22:02 ` |PENDING| " dpdklab
2024-07-11 22:05 ` dpdklab
2024-07-11 22:06 ` dpdklab
2024-07-11 22:06 ` dpdklab
2024-07-11 22:07 ` dpdklab
2024-07-11 22:13 ` dpdklab
2024-07-11 22:14 ` dpdklab
2024-07-11 22:16 ` |FAILURE| " dpdklab
2024-07-11 22:17 ` dpdklab
2024-07-11 22:18 ` |PENDING| " dpdklab
2024-07-11 22:19 ` |FAILURE| " dpdklab
2024-07-11 22:19 ` dpdklab
2024-07-11 22:19 ` dpdklab
2024-07-11 22:20 ` dpdklab
2024-07-11 22:22 ` dpdklab
2024-07-11 22:23 ` dpdklab
2024-07-11 22:23 ` dpdklab
2024-07-11 22:23 ` dpdklab
2024-07-11 22:24 ` |PENDING| " dpdklab
2024-07-11 22:24 ` |FAILURE| " dpdklab
2024-07-11 22:43 ` |PENDING| " dpdklab
2024-07-11 22:57 ` dpdklab
2024-07-11 22:58 ` |FAILURE| " dpdklab
2024-07-11 23:01 ` |PENDING| " dpdklab
2024-07-11 23:02 ` dpdklab
2024-07-11 23:03 ` dpdklab
2024-07-11 23:14 ` |SUCCESS| " dpdklab
2024-07-11 23:26 ` |FAILURE| " dpdklab
2024-07-11 23:34 ` dpdklab
2024-07-11 23:35 ` dpdklab
2024-07-11 23:40 ` dpdklab
2024-07-11 23:47 ` dpdklab
2024-07-12  2:29 ` |SUCCESS| " dpdklab
2024-07-13  0:46 ` dpdklab
2024-07-14  6:33 ` dpdklab
2024-07-14 12:54 ` dpdklab
2024-07-14 21:10 ` dpdklab
2024-07-14 21:16 ` 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=66903428.050a0220.b131.fb10SMTPIN_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).