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| pw148941 [PATCH] [v1,1/1] usertools/devbind: fix NUMA node
Date: Fri, 29 Nov 2024 12:39:54 -0800 (PST)	[thread overview]
Message-ID: <674a269a.170a0220.31be84.bf84SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <890de9246f00065a30398729d4c2baf047002584.1732873932.git.anatoly.burakov@intel.com>

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

_Functional Testing PASS_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Friday, November 29 2024 09:52:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c0f5a9dd74f41688660e4ef84487a175ee44a54a

148941 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#200047

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  |
+-----------------+--------+
| dynamic_queue   |  PASS  |
+-----------------+--------+
| ipv4_reassembly |  PASS  |
+-----------------+--------+
| rxtx_callbacks  |  PASS  |
+-----------------+--------+
| tso             |  PASS  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-11-29 20:39 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <890de9246f00065a30398729d4c2baf047002584.1732873932.git.anatoly.burakov@intel.com>
2024-11-29  9:27 ` |SUCCESS| pw148941 [PATCH v1 1/1] usertools/devbind: fix NUMA node display qemudev
2024-11-29  9:32 ` qemudev
2024-11-29  9:53 ` checkpatch
2024-11-29 10:42 ` 0-day Robot
2024-11-29 18:58 ` |PENDING| pw148941 [PATCH] [v1,1/1] usertools/devbind: fix NUMA node dpdklab
2024-11-29 19:01 ` dpdklab
2024-11-29 19:03 ` |SUCCESS| " dpdklab
2024-11-29 19:05 ` dpdklab
2024-11-29 19:05 ` |PENDING| " dpdklab
2024-11-29 19:16 ` |SUCCESS| " dpdklab
2024-11-29 19:17 ` dpdklab
2024-11-29 19:18 ` dpdklab
2024-11-29 19:25 ` dpdklab
2024-11-29 19:39 ` dpdklab
2024-11-29 19:44 ` dpdklab
2024-11-29 19:45 ` dpdklab
2024-11-29 19:45 ` |WARNING| " dpdklab
2024-11-29 19:49 ` |SUCCESS| " dpdklab
2024-11-29 19:54 ` dpdklab
2024-11-29 19:59 ` dpdklab
2024-11-29 20:01 ` |PENDING| " dpdklab
2024-11-29 20:14 ` |SUCCESS| " dpdklab
2024-11-29 20:15 ` dpdklab
2024-11-29 20:20 ` dpdklab
2024-11-29 20:23 ` dpdklab
2024-11-29 20:27 ` dpdklab
2024-11-29 20:29 ` dpdklab
2024-11-29 20:39 ` dpdklab [this message]
2024-11-29 20:43 ` |PENDING| " dpdklab
2024-11-29 21:15 ` |SUCCESS| " dpdklab
2024-11-29 21:23 ` |WARNING| " dpdklab
2024-11-29 21:29 ` |SUCCESS| " dpdklab
2024-11-29 21:48 ` dpdklab
2024-11-29 22:15 ` dpdklab
2024-11-29 22:19 ` dpdklab
2024-11-29 22:20 ` |WARNING| " dpdklab
2024-11-29 22:22 ` |SUCCESS| " dpdklab
2024-11-29 22:38 ` |WARNING| " dpdklab
2024-11-29 22:43 ` |SUCCESS| " 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=674a269a.170a0220.31be84.bf84SMTPIN_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).