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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126530 [PATCH] [1/1] app/test: resolve mbuf_test application failure
Date: Wed, 26 Apr 2023 21:23:50 -0700 (PDT)	[thread overview]
Message-ID: <6449f8d6.810a0220.819c8.f37cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126530

_Testing PASS_

Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Wednesday, April 26 2023 09:27:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d03446724972d2a1bb645ce7f3e64f5ef0203d61

126530 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+
| RHEL 7           | PASS     |
+------------------+----------+


openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1-2

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-27  4:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27  4:23 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-28 20:24 dpdklab
2023-04-28 20:17 dpdklab
2023-04-28 18:15 dpdklab
2023-04-28 15:48 dpdklab
2023-04-27 23:13 dpdklab
2023-04-27 20:39 dpdklab
2023-04-27  7:45 dpdklab
2023-04-27  7:44 dpdklab
2023-04-27  6:38 dpdklab
2023-04-27  4:54 dpdklab
2023-04-27  4:53 dpdklab
2023-04-27  4:49 dpdklab
2023-04-27  4:43 dpdklab
2023-04-27  4:33 dpdklab
2023-04-27  4:29 dpdklab
2023-04-27  4:23 dpdklab
2023-04-27  4:15 dpdklab
2023-04-27  4:14 dpdklab
2023-04-27  4:07 dpdklab
2023-04-27  4:07 dpdklab
2023-04-27  4:03 dpdklab
2023-04-27  3:48 dpdklab
2023-04-27  3:36 dpdklab
2023-04-27  3:30 dpdklab
2023-04-27  3:30 dpdklab
2023-04-27  3:28 dpdklab
2023-04-27  3:24 dpdklab
     [not found] <20230426092750.2423850-1-rkudurumalla@marvell.com>
2023-04-26  9:20 ` |SUCCESS| pw126530 [PATCH 1/1] " qemudev
2023-04-26  9:24 ` qemudev
2023-04-26  9:28 ` checkpatch
2023-04-26 10:39 ` 0-day Robot

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=6449f8d6.810a0220.819c8.f37cSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).