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| pw142074-142081 [PATCH] [8/8] mempool/dpaax: cache free op
Date: Wed, 03 Jul 2024 13:57:16 -0700 (PDT)	[thread overview]
Message-ID: <6685bb2c.050a0220.be872.1551SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240703111644.1523242-9-vanshika.shukla@nxp.com>

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

_Functional Testing PASS_

Submitter: None <vanshika.shukla@nxp.com>
Date: Wednesday, July 03 2024 11:16:44 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fbba6db3640f9f623c29c452e1a6b057073e81d2

142074-142081 --> functional testing pass

Test environment and result as below:

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

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
Target: Unknown

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
Target: Unknown

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


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

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-03 20:57 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240703111644.1523242-9-vanshika.shukla@nxp.com>
2024-07-03 10:51 ` |SUCCESS| pw142074-142081 [PATCH 8/8] mempool/dpaax: cache free optimization qemudev
2024-07-03 10:56 ` qemudev
2024-07-03 11:18 ` |SUCCESS| pw142081 " checkpatch
2024-07-03 12:04 ` 0-day Robot
2024-07-03 19:56 ` |SUCCESS| pw142074-142081 [PATCH] [8/8] mempool/dpaax: cache free op dpdklab
2024-07-03 19:58 ` |PENDING| " dpdklab
2024-07-03 20:00 ` |SUCCESS| " dpdklab
2024-07-03 20:01 ` dpdklab
2024-07-03 20:04 ` dpdklab
2024-07-03 20:05 ` dpdklab
2024-07-03 20:06 ` dpdklab
2024-07-03 20:07 ` dpdklab
2024-07-03 20:07 ` |PENDING| " dpdklab
2024-07-03 20:13 ` dpdklab
2024-07-03 20:16 ` |SUCCESS| " dpdklab
2024-07-03 20:17 ` |PENDING| " dpdklab
2024-07-03 20:19 ` dpdklab
2024-07-03 20:19 ` dpdklab
2024-07-03 20:20 ` |SUCCESS| " dpdklab
2024-07-03 20:21 ` |PENDING| " dpdklab
2024-07-03 20:22 ` dpdklab
2024-07-03 20:23 ` dpdklab
2024-07-03 20:24 ` |SUCCESS| " dpdklab
2024-07-03 20:25 ` |PENDING| " dpdklab
2024-07-03 20:25 ` |SUCCESS| " dpdklab
2024-07-03 20:26 ` |PENDING| " dpdklab
2024-07-03 20:26 ` dpdklab
2024-07-03 20:28 ` dpdklab
2024-07-03 20:28 ` dpdklab
2024-07-03 20:29 ` dpdklab
2024-07-03 20:29 ` |FAILURE| " dpdklab
2024-07-03 20:31 ` dpdklab
2024-07-03 20:32 ` |PENDING| " dpdklab
2024-07-03 20:35 ` dpdklab
2024-07-03 20:37 ` dpdklab
2024-07-03 20:40 ` |FAILURE| " dpdklab
2024-07-03 20:41 ` dpdklab
2024-07-03 20:42 ` |PENDING| " dpdklab
2024-07-03 20:44 ` |SUCCESS| " dpdklab
2024-07-03 20:45 ` |FAILURE| " dpdklab
2024-07-03 20:46 ` |SUCCESS| " dpdklab
2024-07-03 20:47 ` |PENDING| " dpdklab
2024-07-03 20:47 ` |FAILURE| " dpdklab
2024-07-03 20:49 ` |PENDING| " dpdklab
2024-07-03 20:49 ` |FAILURE| " dpdklab
2024-07-03 20:49 ` |PENDING| " dpdklab
2024-07-03 20:51 ` |FAILURE| " dpdklab
2024-07-03 20:53 ` dpdklab
2024-07-03 20:54 ` |PENDING| " dpdklab
2024-07-03 20:54 ` |FAILURE| " dpdklab
2024-07-03 20:55 ` dpdklab
2024-07-03 20:56 ` dpdklab
2024-07-03 20:57 ` dpdklab [this message]
2024-07-03 20:57 ` dpdklab
2024-07-03 20:58 ` dpdklab
2024-07-03 20:58 ` dpdklab
2024-07-03 20:58 ` |WARNING| " dpdklab
2024-07-03 20:59 ` |FAILURE| " dpdklab
2024-07-03 21:00 ` dpdklab
2024-07-03 21:01 ` dpdklab
2024-07-03 21:01 ` dpdklab
2024-07-03 21:02 ` dpdklab
2024-07-03 21:03 ` dpdklab
2024-07-03 21:03 ` dpdklab
2024-07-03 21:03 ` dpdklab
2024-07-03 21:03 ` dpdklab
2024-07-03 21:04 ` dpdklab
2024-07-03 21:05 ` dpdklab
2024-07-03 21:05 ` dpdklab
2024-07-03 21:06 ` dpdklab
2024-07-03 21:09 ` dpdklab
2024-07-03 21:10 ` |PENDING| " dpdklab
2024-07-03 21:11 ` |FAILURE| " dpdklab
2024-07-03 21:12 ` dpdklab
2024-07-03 21:13 ` dpdklab
2024-07-03 21:15 ` dpdklab
2024-07-03 21:16 ` dpdklab
2024-07-03 21:17 ` dpdklab
2024-07-03 21:22 ` dpdklab
2024-07-03 21:23 ` dpdklab
2024-07-03 21:25 ` dpdklab
2024-07-03 21:25 ` dpdklab
2024-07-03 21:26 ` dpdklab
2024-07-03 21:26 ` dpdklab
2024-07-03 21:30 ` dpdklab
2024-07-03 21:32 ` dpdklab
2024-07-03 21:32 ` dpdklab
2024-07-03 21:33 ` dpdklab
2024-07-03 21:33 ` dpdklab
2024-07-03 21:37 ` dpdklab
2024-07-03 21:39 ` dpdklab
2024-07-03 21:45 ` dpdklab
2024-07-03 21:48 ` dpdklab
2024-07-03 21:54 ` dpdklab
2024-07-03 21:59 ` dpdklab
2024-07-03 22:03 ` dpdklab
2024-07-03 22:12 ` dpdklab
2024-07-03 22:12 ` dpdklab
2024-07-04  2:18 ` |PENDING| " dpdklab
2024-07-04  2:20 ` dpdklab
2024-07-04  2:23 ` |FAILURE| " dpdklab
2024-07-04  2:28 ` dpdklab
2024-07-04  2:32 ` dpdklab
2024-07-04  2:36 ` dpdklab
2024-07-04  2:40 ` dpdklab
2024-07-04  2:48 ` dpdklab
2024-07-04  3:06 ` dpdklab
2024-07-04  3:14 ` dpdklab
2024-07-04  3:17 ` dpdklab
2024-07-04  3:25 ` dpdklab
2024-07-04  3:28 ` dpdklab
2024-07-04  3:36 ` dpdklab
2024-07-04  3:37 ` dpdklab
2024-07-04  3:44 ` dpdklab
2024-07-04 21:41 ` dpdklab
2024-07-04 23:25 ` 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=6685bb2c.050a0220.be872.1551SMTPIN_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).