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| pw144430 [PATCH] [v2] mbuf: fix strict aliasing error in a
Date: Wed, 25 Sep 2024 11:59:39 -0700 (PDT)	[thread overview]
Message-ID: <66f45d9b.050a0220.977dc.a081SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240925154053.80861-2-rjarry@redhat.com>

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

_Functional Testing PASS_

Submitter: Robin Jarry <rjarry@redhat.com>
Date: Wednesday, September 25 2024 15:40:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144430 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#183364

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

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-25 18:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240925154053.80861-2-rjarry@redhat.com>
2024-09-25 15:14 ` |SUCCESS| pw144430 [PATCH dpdk v2] mbuf: fix strict aliasing error in allocator qemudev
2024-09-25 15:19 ` qemudev
2024-09-25 15:41 ` checkpatch
2024-09-25 16:34 ` 0-day Robot
2024-09-25 18:35 ` |SUCCESS| pw144430 [PATCH] [v2] mbuf: fix strict aliasing error in a dpdklab
2024-09-25 18:38 ` |PENDING| " dpdklab
2024-09-25 18:47 ` dpdklab
2024-09-25 18:49 ` |FAILURE| " dpdklab
2024-09-25 18:51 ` |SUCCESS| " dpdklab
2024-09-25 18:54 ` dpdklab
2024-09-25 18:56 ` |PENDING| " dpdklab
2024-09-25 18:56 ` dpdklab
2024-09-25 18:59 ` dpdklab [this message]
2024-09-25 19:00 ` dpdklab
2024-09-25 19:02 ` |SUCCESS| " dpdklab
2024-09-25 19:03 ` dpdklab
2024-09-25 19:24 ` dpdklab
2024-09-25 19:26 ` dpdklab
2024-09-25 19:46 ` dpdklab
2024-09-25 19:58 ` dpdklab
2024-09-25 20:05 ` dpdklab
2024-09-25 21:17 ` dpdklab
2024-09-25 22:29 ` 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=66f45d9b.050a0220.977dc.a081SMTPIN_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).