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| pw144863 [PATCH] [RFC,v14] mempool: fix mempool cache size
Date: Tue, 01 Oct 2024 09:30:49 -0700 (PDT)	[thread overview]
Message-ID: <66fc23b9.920a0220.240e1e.b9f4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241001134131.2130079-1-mb@smartsharesystems.com>

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

_Functional Testing PASS_

Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Tuesday, October 01 2024 13:41:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:bf0ff8df59c7e32f95c0b542cc4a7918f8a3da84

144863 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#184581

Test environment and result as below:

Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-01 16:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241001134131.2130079-1-mb@smartsharesystems.com>
2024-10-01 13:32 ` |SUCCESS| pw144863 [RFC PATCH v14] " qemudev
2024-10-01 13:36 ` qemudev
2024-10-01 13:43 ` checkpatch
2024-10-01 15:05 ` 0-day Robot
2024-10-01 16:09 ` |SUCCESS| pw144863 [PATCH] [RFC,v14] " dpdklab
2024-10-01 16:14 ` dpdklab
2024-10-01 16:16 ` dpdklab
2024-10-01 16:20 ` dpdklab
2024-10-01 16:30 ` dpdklab [this message]
2024-10-01 16:32 ` dpdklab
2024-10-01 17:17 ` |PENDING| " dpdklab
2024-10-01 17:42 ` |SUCCESS| " dpdklab
2024-10-01 18:15 ` |PENDING| " dpdklab
2024-10-01 19:02 ` |SUCCESS| " dpdklab
2024-10-01 19:43 ` dpdklab
2024-10-01 20:58 ` |PENDING| " dpdklab
2024-10-01 22:39 ` |SUCCESS| " dpdklab
2024-10-01 22:46 ` dpdklab
2024-10-01 23:08 ` dpdklab
2024-10-02  1:17 ` dpdklab
2024-10-02  1:58 ` dpdklab
2024-10-02  2:05 ` dpdklab
2024-10-02  9:45 ` 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=66fc23b9.920a0220.240e1e.b9f4SMTPIN_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).