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| pw141990 [PATCH] [v2] buildtools: fix invalid symbols
Date: Mon, 01 Jul 2024 10:00:29 -0700 (PDT)	[thread overview]
Message-ID: <6682e0ad.170a0220.ae841.2f31SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240701103315.835249-1-mingjinx.ye@intel.com>

Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/141990

_Functional Testing PASS_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Monday, July 01 2024 10:33:15 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b

141990 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: Unknown

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| cmdline         |  PASS  |
+-----------------+--------+
| coremask        |  PASS  |
+-----------------+--------+
| ipv4_reassembly |  PASS  |
+-----------------+--------+
| l2fwd           |  PASS  |
+-----------------+--------+
| rxtx_callbacks  |  PASS  |
+-----------------+--------+
| tso             |  PASS  |
+-----------------+--------+


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

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-01 17:00 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240701103315.835249-1-mingjinx.ye@intel.com>
2024-07-01 10:37 ` |SUCCESS| pw141990 [PATCH v2] " qemudev
2024-07-01 10:41 ` qemudev
2024-07-01 10:56 ` checkpatch
2024-07-01 11:45 ` 0-day Robot
2024-07-01 16:44 ` |SUCCESS| pw141990 [PATCH] [v2] " dpdklab
2024-07-01 16:45 ` dpdklab
2024-07-01 16:51 ` dpdklab
2024-07-01 16:56 ` dpdklab
2024-07-01 16:57 ` |PENDING| " dpdklab
2024-07-01 17:00 ` dpdklab [this message]
2024-07-01 17:02 ` dpdklab
2024-07-01 17:03 ` dpdklab
2024-07-01 17:07 ` dpdklab
2024-07-01 17:08 ` dpdklab
2024-07-01 17:08 ` dpdklab
2024-07-01 17:08 ` dpdklab
2024-07-01 17:15 ` |SUCCESS| " dpdklab
2024-07-01 17:17 ` |PENDING| " dpdklab
2024-07-01 17:19 ` dpdklab
2024-07-01 17:20 ` dpdklab
2024-07-01 17:21 ` dpdklab
2024-07-01 17:22 ` dpdklab
2024-07-01 17:26 ` |SUCCESS| " dpdklab
2024-07-01 17:30 ` |PENDING| " dpdklab
2024-07-01 17:33 ` dpdklab
2024-07-01 17:35 ` dpdklab
2024-07-01 17:37 ` dpdklab
2024-07-01 17:37 ` dpdklab
2024-07-01 17:38 ` dpdklab
2024-07-01 17:40 ` dpdklab
2024-07-01 17:42 ` dpdklab
2024-07-01 17:46 ` |SUCCESS| " dpdklab
2024-07-01 17:46 ` |PENDING| " dpdklab
2024-07-01 17:47 ` dpdklab
2024-07-01 17:48 ` dpdklab
2024-07-01 17:48 ` dpdklab
2024-07-01 17:50 ` dpdklab
2024-07-01 17:50 ` dpdklab
2024-07-01 17:52 ` dpdklab
2024-07-01 17:52 ` dpdklab
2024-07-01 17:54 ` dpdklab
2024-07-01 17:55 ` dpdklab
2024-07-01 17:55 ` dpdklab
2024-07-01 17:56 ` dpdklab
2024-07-01 17:56 ` dpdklab
2024-07-01 17:56 ` dpdklab
2024-07-01 17:58 ` dpdklab
2024-07-01 17:58 ` dpdklab
2024-07-01 17:58 ` dpdklab
2024-07-01 17:59 ` dpdklab
2024-07-01 17:59 ` dpdklab
2024-07-01 18:00 ` dpdklab
2024-07-01 18:01 ` dpdklab
2024-07-01 18:02 ` dpdklab
2024-07-01 18:04 ` dpdklab
2024-07-01 18:05 ` dpdklab
2024-07-01 18:06 ` dpdklab
2024-07-01 18:07 ` dpdklab
2024-07-01 18:07 ` dpdklab
2024-07-01 18:08 ` dpdklab
2024-07-01 18:08 ` dpdklab
2024-07-01 18:09 ` dpdklab
2024-07-01 18:10 ` dpdklab
2024-07-01 18:11 ` dpdklab
2024-07-01 18:13 ` dpdklab
2024-07-01 18:13 ` dpdklab
2024-07-01 18:15 ` |SUCCESS| " dpdklab
2024-07-01 18:16 ` |PENDING| " dpdklab
2024-07-01 18:16 ` dpdklab
2024-07-01 18:16 ` |SUCCESS| " dpdklab
2024-07-01 18:17 ` |PENDING| " dpdklab
2024-07-01 18:19 ` dpdklab
2024-07-01 18:21 ` dpdklab
2024-07-01 18:26 ` dpdklab
2024-07-01 18:27 ` |SUCCESS| " dpdklab
2024-07-01 18:27 ` |PENDING| " dpdklab
2024-07-01 18:30 ` dpdklab
2024-07-01 18:40 ` |SUCCESS| " dpdklab
2024-07-01 18:44 ` |PENDING| " dpdklab
2024-07-01 18:44 ` dpdklab
2024-07-01 18:46 ` dpdklab
2024-07-01 18:47 ` dpdklab
2024-07-01 18:47 ` dpdklab
2024-07-01 18:49 ` dpdklab
2024-07-01 18:51 ` dpdklab
2024-07-01 18:53 ` dpdklab
2024-07-01 18:54 ` dpdklab
2024-07-01 18:55 ` dpdklab
2024-07-01 18:56 ` |SUCCESS| " dpdklab
2024-07-01 18:56 ` dpdklab
2024-07-01 18:57 ` |PENDING| " dpdklab
2024-07-01 18:59 ` dpdklab
2024-07-01 19:02 ` dpdklab
2024-07-01 19:02 ` dpdklab
2024-07-01 19:04 ` dpdklab
2024-07-01 19:05 ` dpdklab
2024-07-01 19:07 ` dpdklab
2024-07-01 19:09 ` dpdklab
2024-07-01 19:10 ` dpdklab
2024-07-01 19:11 ` dpdklab
2024-07-01 19:14 ` dpdklab
2024-07-01 19:15 ` dpdklab
2024-07-01 19:20 ` dpdklab
2024-07-01 19:21 ` dpdklab
2024-07-01 19:22 ` dpdklab
2024-07-01 19:25 ` dpdklab
2024-07-01 19:37 ` |SUCCESS| " dpdklab
2024-07-01 19:39 ` dpdklab
2024-07-02 12:35 ` dpdklab
2024-07-02 12:48 ` 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=6682e0ad.170a0220.ae841.2f31SMTPIN_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).