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| pw143775-143785 [PATCH] [11/11] drivers: use per line logg
Date: Mon, 16 Sep 2024 00:39:47 -0700 (PDT)	[thread overview]
Message-ID: <66e7e0c3.170a0220.1ef2fd.90e1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240907145433.1479091-12-david.marchand@redhat.com>

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

_Functional Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Saturday, September 07 2024 14:54:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143775-143785 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#180618

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-16  7:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240907145433.1479091-12-david.marchand@redhat.com>
2024-09-07 14:30 ` |SUCCESS| pw143775-143785 [PATCH 11/11] drivers: use per line logging in helpers qemudev
2024-09-07 14:35 ` qemudev
2024-09-07 14:57 ` |WARNING| pw143785 " checkpatch
2024-09-07 15:44 ` |SUCCESS| " 0-day Robot
2024-09-09 21:51 ` |SUCCESS| pw143775-143785 [PATCH] [11/11] drivers: use per line logg dpdklab
2024-09-09 22:12 ` dpdklab
2024-09-09 22:33 ` dpdklab
2024-09-09 22:50 ` |PENDING| " dpdklab
2024-09-09 22:50 ` dpdklab
2024-09-09 23:02 ` |SUCCESS| " dpdklab
2024-09-09 23:03 ` dpdklab
2024-09-09 23:32 ` |PENDING| " dpdklab
2024-09-10  0:33 ` |FAILURE| " dpdklab
2024-09-10  0:37 ` dpdklab
2024-09-10  1:11 ` |WARNING| " dpdklab
2024-09-10  2:01 ` |PENDING| " dpdklab
2024-09-10  3:31 ` |FAILURE| " dpdklab
2024-09-10  3:57 ` |SUCCESS| " dpdklab
2024-09-10  4:32 ` |WARNING| " dpdklab
2024-09-10  5:25 ` |SUCCESS| " dpdklab
2024-09-10  5:30 ` dpdklab
2024-09-10  5:35 ` dpdklab
2024-09-10  5:48 ` |FAILURE| " dpdklab
2024-09-10  5:55 ` dpdklab
2024-09-10  6:02 ` |SUCCESS| " dpdklab
2024-09-10 13:44 ` dpdklab
2024-09-16  7:39 ` dpdklab [this message]
2024-09-16 15:31 ` |FAILURE| " 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=66e7e0c3.170a0220.1ef2fd.90e1SMTPIN_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).