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| pw143201-143202 [PATCH] [v1,2/2] dts: checksum offload tes
Date: Fri, 16 Aug 2024 08:06:01 -0700 (PDT)	[thread overview]
Message-ID: <66bf6ad9.920a0220.24c44f.cb5eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240816142031.15150-3-dmarx@iol.unh.edu>

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

_Functional Testing PASS_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Friday, August 16 2024 14:20:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143201-143202 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#175608

Test environment and result as below:

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


Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps

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


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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-16 15:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240816142031.15150-3-dmarx@iol.unh.edu>
2024-08-16 13:58 ` |SUCCESS| pw143201-143202 [PATCH v1 2/2] dts: checksum offload test suite qemudev
2024-08-16 14:03 ` qemudev
2024-08-16 14:22 ` |SUCCESS| pw143202 " checkpatch
2024-08-16 14:43 ` |SUCCESS| pw143201-143202 [PATCH] [v1,2/2] dts: checksum offload tes dpdklab
2024-08-16 14:48 ` dpdklab
2024-08-16 14:55 ` |PENDING| " dpdklab
2024-08-16 14:59 ` dpdklab
2024-08-16 15:06 ` dpdklab [this message]
2024-08-16 15:15 ` |SUCCESS| " dpdklab
2024-08-16 15:21 ` dpdklab
2024-08-16 15:22 ` |SUCCESS| pw143202 [PATCH v1 2/2] dts: checksum offload test suite 0-day Robot
2024-08-16 15:27 ` |SUCCESS| pw143201-143202 [PATCH] [v1,2/2] dts: checksum offload tes dpdklab
2024-08-16 15:30 ` dpdklab
2024-08-16 15:36 ` dpdklab
2024-08-16 15:39 ` dpdklab
2024-08-16 15:41 ` dpdklab
2024-08-16 15:46 ` dpdklab
2024-08-16 15:49 ` dpdklab
2024-08-16 16:05 ` dpdklab
2024-08-16 16:16 ` dpdklab
2024-08-16 17:08 ` dpdklab
2024-08-16 17:08 ` dpdklab
2024-08-16 22:09 ` |WARNING| " 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=66bf6ad9.920a0220.24c44f.cb5eSMTPIN_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).