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| pw142293 [PATCH] net/cpfl: fix build error for debian 32-b
Date: Sun, 14 Jul 2024 01:04:58 -0700 (PDT)	[thread overview]
Message-ID: <669386aa.050a0220.10005.9baaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240710145351.599031-1-bruce.richardson@intel.com>

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

_Functional Testing PASS_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, July 10 2024 14:53:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e014773daacdb2f4be17061352592e5bb83a1d3f

142293 --> functional testing pass

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


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


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

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-14  8:05 UTC|newest]

Thread overview: 119+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240710145351.599031-1-bruce.richardson@intel.com>
2024-07-10 14:31 ` |SUCCESS| pw142293 [PATCH] net/cpfl: fix build error for debian 32-bit qemudev
2024-07-10 14:35 ` qemudev
2024-07-10 14:55 ` checkpatch
2024-07-10 16:03 ` 0-day Robot
2024-07-10 17:35 ` |PENDING| pw142293 [PATCH] net/cpfl: fix build error for debian 32-b dpdklab
2024-07-10 17:37 ` dpdklab
2024-07-10 17:39 ` |SUCCESS| " dpdklab
2024-07-10 17:39 ` dpdklab
2024-07-10 17:41 ` dpdklab
2024-07-10 17:46 ` |PENDING| " dpdklab
2024-07-10 17:46 ` |SUCCESS| " dpdklab
2024-07-10 17:51 ` |PENDING| " dpdklab
2024-07-10 17:58 ` |SUCCESS| " dpdklab
2024-07-10 17:59 ` |PENDING| " dpdklab
2024-07-10 18:00 ` |SUCCESS| " dpdklab
2024-07-10 18:00 ` |PENDING| " dpdklab
2024-07-10 18:00 ` |SUCCESS| " dpdklab
2024-07-10 18:00 ` dpdklab
2024-07-10 18:00 ` |PENDING| " dpdklab
2024-07-10 18:02 ` |SUCCESS| " dpdklab
2024-07-10 18:02 ` |PENDING| " dpdklab
2024-07-10 18:04 ` |SUCCESS| " dpdklab
2024-07-10 18:05 ` dpdklab
2024-07-10 18:06 ` |PENDING| " dpdklab
2024-07-10 18:09 ` dpdklab
2024-07-10 18:10 ` |SUCCESS| " dpdklab
2024-07-10 18:11 ` |PENDING| " dpdklab
2024-07-10 18:12 ` dpdklab
2024-07-10 18:12 ` dpdklab
2024-07-10 18:13 ` dpdklab
2024-07-10 18:17 ` dpdklab
2024-07-10 18:17 ` dpdklab
2024-07-10 18:21 ` dpdklab
2024-07-10 18:22 ` dpdklab
2024-07-10 18:24 ` dpdklab
2024-07-10 18:26 ` dpdklab
2024-07-10 18:30 ` dpdklab
2024-07-10 18:32 ` dpdklab
2024-07-10 18:32 ` dpdklab
2024-07-10 18:35 ` dpdklab
2024-07-10 18:37 ` |SUCCESS| " dpdklab
2024-07-10 18:40 ` dpdklab
2024-07-10 18:44 ` |PENDING| " dpdklab
2024-07-10 18:48 ` dpdklab
2024-07-10 18:48 ` dpdklab
2024-07-10 18:50 ` dpdklab
2024-07-10 18:50 ` dpdklab
2024-07-10 18:54 ` dpdklab
2024-07-10 18:55 ` dpdklab
2024-07-10 18:55 ` dpdklab
2024-07-10 18:56 ` dpdklab
2024-07-10 18:56 ` dpdklab
2024-07-10 18:56 ` dpdklab
2024-07-10 18:57 ` dpdklab
2024-07-10 18:57 ` dpdklab
2024-07-10 18:57 ` dpdklab
2024-07-10 18:57 ` dpdklab
2024-07-10 19:00 ` |SUCCESS| " dpdklab
2024-07-10 19:01 ` |PENDING| " dpdklab
2024-07-10 19:01 ` dpdklab
2024-07-10 19:01 ` dpdklab
2024-07-10 19:02 ` dpdklab
2024-07-10 19:02 ` dpdklab
2024-07-10 19:02 ` dpdklab
2024-07-10 19:03 ` dpdklab
2024-07-10 19:04 ` dpdklab
2024-07-10 19:04 ` dpdklab
2024-07-10 19:04 ` dpdklab
2024-07-10 19:05 ` dpdklab
2024-07-10 19:05 ` dpdklab
2024-07-10 19:05 ` dpdklab
2024-07-10 19:06 ` dpdklab
2024-07-10 19:08 ` dpdklab
2024-07-10 19:08 ` dpdklab
2024-07-10 19:08 ` dpdklab
2024-07-10 19:11 ` dpdklab
2024-07-10 19:11 ` dpdklab
2024-07-10 19:13 ` dpdklab
2024-07-10 19:13 ` dpdklab
2024-07-10 19:14 ` dpdklab
2024-07-10 19:15 ` dpdklab
2024-07-10 19:15 ` dpdklab
2024-07-10 19:16 ` dpdklab
2024-07-10 19:17 ` dpdklab
2024-07-10 19:19 ` |SUCCESS| " dpdklab
2024-07-10 19:20 ` |PENDING| " dpdklab
2024-07-10 19:20 ` dpdklab
2024-07-10 19:20 ` dpdklab
2024-07-10 19:21 ` dpdklab
2024-07-10 19:25 ` dpdklab
2024-07-10 19:27 ` dpdklab
2024-07-10 19:28 ` dpdklab
2024-07-10 19:29 ` dpdklab
2024-07-10 19:36 ` |SUCCESS| " dpdklab
2024-07-10 19:42 ` |PENDING| " dpdklab
2024-07-10 19:50 ` dpdklab
2024-07-10 19:51 ` dpdklab
2024-07-10 19:51 ` dpdklab
2024-07-10 19:54 ` dpdklab
2024-07-10 19:55 ` dpdklab
2024-07-10 19:56 ` dpdklab
2024-07-10 19:56 ` dpdklab
2024-07-10 19:58 ` dpdklab
2024-07-10 20:00 ` dpdklab
2024-07-10 20:04 ` dpdklab
2024-07-10 20:07 ` dpdklab
2024-07-10 20:09 ` dpdklab
2024-07-10 20:12 ` dpdklab
2024-07-10 20:13 ` dpdklab
2024-07-10 20:13 ` dpdklab
2024-07-10 20:17 ` |SUCCESS| " dpdklab
2024-07-10 20:39 ` dpdklab
2024-07-11 15:11 ` dpdklab
2024-07-11 15:52 ` dpdklab
2024-07-13  9:55 ` dpdklab
2024-07-14  8:04 ` dpdklab [this message]
2024-07-14 14:37 ` dpdklab
2024-07-15  1:17 ` dpdklab
2024-07-15  1:21 ` 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=669386aa.050a0220.10005.9baaSMTPIN_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).