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| pw142908 [PATCH] net/iavf: fix core dump when the link is
Date: Mon, 05 Aug 2024 20:03:19 -0700 (PDT)	[thread overview]
Message-ID: <66b19277.050a0220.c68b4.ba15SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240806003527.2901320-1-kaiwenx.deng@intel.com>

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

_Functional Testing PASS_

Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Tuesday, August 06 2024 00:35:27 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b017bdc4c25e2cd6733a9363e9c566b95834cc4

142908 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#173149

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

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-06  3:03 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240806003527.2901320-1-kaiwenx.deng@intel.com>
2024-08-06  1:13 ` |SUCCESS| pw142908 [PATCH] net/iavf: fix core dump when the link is unstable qemudev
2024-08-06  1:17 ` qemudev
2024-08-06  1:39 ` checkpatch
2024-08-06  2:03 ` |SUCCESS| pw142908 [PATCH] net/iavf: fix core dump when the link is dpdklab
2024-08-06  2:09 ` |PENDING| " dpdklab
2024-08-06  2:11 ` |SUCCESS| " dpdklab
2024-08-06  2:14 ` dpdklab
2024-08-06  2:16 ` |PENDING| " dpdklab
2024-08-06  2:16 ` dpdklab
2024-08-06  2:17 ` dpdklab
2024-08-06  2:17 ` dpdklab
2024-08-06  2:17 ` dpdklab
2024-08-06  2:19 ` dpdklab
2024-08-06  2:20 ` dpdklab
2024-08-06  2:21 ` dpdklab
2024-08-06  2:22 ` dpdklab
2024-08-06  2:22 ` dpdklab
2024-08-06  2:23 ` dpdklab
2024-08-06  2:23 ` dpdklab
2024-08-06  2:25 ` dpdklab
2024-08-06  2:26 ` |SUCCESS| " dpdklab
2024-08-06  2:26 ` |PENDING| " dpdklab
2024-08-06  2:27 ` dpdklab
2024-08-06  2:27 ` dpdklab
2024-08-06  2:28 ` dpdklab
2024-08-06  2:28 ` dpdklab
2024-08-06  2:28 ` dpdklab
2024-08-06  2:28 ` dpdklab
2024-08-06  2:29 ` |SUCCESS| " dpdklab
2024-08-06  2:30 ` |PENDING| " dpdklab
2024-08-06  2:30 ` dpdklab
2024-08-06  2:31 ` |SUCCESS| " dpdklab
2024-08-06  2:31 ` |PENDING| " dpdklab
2024-08-06  2:33 ` dpdklab
2024-08-06  2:34 ` dpdklab
2024-08-06  2:34 ` dpdklab
2024-08-06  2:34 ` dpdklab
2024-08-06  2:35 ` dpdklab
2024-08-06  2:36 ` dpdklab
2024-08-06  2:36 ` dpdklab
2024-08-06  2:36 ` dpdklab
2024-08-06  2:37 ` dpdklab
2024-08-06  2:37 ` dpdklab
2024-08-06  2:38 ` dpdklab
2024-08-06  2:40 ` |SUCCESS| " dpdklab
2024-08-06  2:41 ` |PENDING| " dpdklab
2024-08-06  2:42 ` |SUCCESS| " dpdklab
2024-08-06  2:42 ` |PENDING| " dpdklab
2024-08-06  2:42 ` |SUCCESS| pw142908 [PATCH] net/iavf: fix core dump when the link is unstable 0-day Robot
2024-08-06  2:43 ` |PENDING| pw142908 [PATCH] net/iavf: fix core dump when the link is dpdklab
2024-08-06  2:43 ` dpdklab
2024-08-06  2:43 ` |SUCCESS| " dpdklab
2024-08-06  2:43 ` |PENDING| " dpdklab
2024-08-06  2:43 ` dpdklab
2024-08-06  2:43 ` |SUCCESS| " dpdklab
2024-08-06  2:43 ` |PENDING| " dpdklab
2024-08-06  2:43 ` |SUCCESS| " dpdklab
2024-08-06  2:44 ` |PENDING| " dpdklab
2024-08-06  2:44 ` dpdklab
2024-08-06  2:45 ` dpdklab
2024-08-06  2:46 ` dpdklab
2024-08-06  2:46 ` dpdklab
2024-08-06  2:46 ` |SUCCESS| " dpdklab
2024-08-06  2:47 ` |PENDING| " dpdklab
2024-08-06  2:47 ` dpdklab
2024-08-06  2:47 ` dpdklab
2024-08-06  2:48 ` dpdklab
2024-08-06  2:49 ` dpdklab
2024-08-06  2:50 ` dpdklab
2024-08-06  2:51 ` dpdklab
2024-08-06  2:51 ` dpdklab
2024-08-06  2:51 ` dpdklab
2024-08-06  2:52 ` dpdklab
2024-08-06  2:52 ` |SUCCESS| " dpdklab
2024-08-06  2:53 ` |PENDING| " dpdklab
2024-08-06  2:53 ` dpdklab
2024-08-06  2:53 ` dpdklab
2024-08-06  2:53 ` dpdklab
2024-08-06  2:54 ` dpdklab
2024-08-06  2:54 ` dpdklab
2024-08-06  2:55 ` dpdklab
2024-08-06  2:56 ` dpdklab
2024-08-06  2:57 ` dpdklab
2024-08-06  2:58 ` dpdklab
2024-08-06  2:59 ` |SUCCESS| " dpdklab
2024-08-06  3:00 ` |PENDING| " dpdklab
2024-08-06  3:00 ` dpdklab
2024-08-06  3:00 ` dpdklab
2024-08-06  3:02 ` dpdklab
2024-08-06  3:02 ` dpdklab
2024-08-06  3:02 ` |SUCCESS| " dpdklab
2024-08-06  3:02 ` |PENDING| " dpdklab
2024-08-06  3:03 ` dpdklab [this message]
2024-08-06  3:03 ` dpdklab
2024-08-06  3:05 ` dpdklab
2024-08-06  3:06 ` dpdklab
2024-08-06  3:06 ` dpdklab
2024-08-06  3:06 ` dpdklab
2024-08-06  3:08 ` |SUCCESS| " dpdklab
2024-08-06  3:09 ` |PENDING| " dpdklab
2024-08-06  3:10 ` dpdklab
2024-08-06  3:11 ` dpdklab
2024-08-06  3:12 ` dpdklab
2024-08-06  3:13 ` dpdklab
2024-08-06  3:14 ` |SUCCESS| " dpdklab
2024-08-06  3:19 ` |PENDING| " dpdklab
2024-08-06  3:39 ` dpdklab
2024-08-06  3:58 ` dpdklab
2024-08-06  3:59 ` |SUCCESS| " dpdklab
2024-08-06 23:43 ` dpdklab
2024-08-06 23:52 ` dpdklab
2024-08-07  0:06 ` 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=66b19277.050a0220.c68b4.ba15SMTPIN_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).