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| pw135220-135221 [PATCH] [v6,2/2] devtools: add tracepoint
Date: Fri, 15 Dec 2023 01:32:46 -0800 (PST)	[thread overview]
Message-ID: <657c1d3e.810a0220.e3b81.6810SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Ankur Dwivedi <adwivedi@marvell.com>
Date: Friday, December 15 2023 06:43:55 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135220-135221 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| CentOS Stream 8 | PASS     |
+-----------------+----------+
| Fedora 38       | PASS     |
+-----------------+----------+
| RHEL8           | PASS     |
+-----------------+----------+


CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-15  9:32 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15  9:32 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-15 18:17 dpdklab
2023-12-15 13:08 dpdklab
2023-12-15 10:59 dpdklab
2023-12-15 10:45 dpdklab
2023-12-15 10:43 dpdklab
2023-12-15 10:43 dpdklab
2023-12-15 10:43 dpdklab
2023-12-15 10:41 dpdklab
2023-12-15 10:41 dpdklab
2023-12-15 10:39 dpdklab
2023-12-15 10:38 dpdklab
2023-12-15 10:36 dpdklab
2023-12-15 10:36 dpdklab
2023-12-15 10:32 dpdklab
2023-12-15 10:30 dpdklab
2023-12-15 10:30 dpdklab
2023-12-15 10:30 dpdklab
2023-12-15 10:29 dpdklab
2023-12-15 10:28 dpdklab
2023-12-15 10:28 dpdklab
2023-12-15 10:27 dpdklab
2023-12-15 10:27 dpdklab
2023-12-15 10:20 dpdklab
2023-12-15 10:19 dpdklab
2023-12-15 10:19 dpdklab
2023-12-15 10:19 dpdklab
2023-12-15 10:19 dpdklab
2023-12-15 10:18 dpdklab
2023-12-15 10:17 dpdklab
2023-12-15 10:16 dpdklab
2023-12-15 10:16 dpdklab
2023-12-15 10:16 dpdklab
2023-12-15 10:00 dpdklab
2023-12-15  9:59 dpdklab
2023-12-15  9:55 dpdklab
2023-12-15  9:49 dpdklab
2023-12-15  9:48 dpdklab
2023-12-15  9:48 dpdklab
2023-12-15  9:46 dpdklab
2023-12-15  9:43 dpdklab
2023-12-15  9:39 dpdklab
2023-12-15  9:38 dpdklab
2023-12-15  9:37 dpdklab
2023-12-15  9:17 dpdklab
2023-12-15  9:14 dpdklab
2023-12-15  9:14 dpdklab
2023-12-15  9:13 dpdklab
2023-12-15  9:13 dpdklab
2023-12-15  9:11 dpdklab
2023-12-15  9:09 dpdklab
2023-12-15  9:03 dpdklab
2023-12-15  9:02 dpdklab
2023-12-15  9:02 dpdklab
2023-12-15  9:02 dpdklab
2023-12-15  8:59 dpdklab
2023-12-15  8:59 dpdklab
2023-12-15  8:58 dpdklab
2023-12-15  8:57 dpdklab
2023-12-15  8:57 dpdklab
2023-12-15  8:56 dpdklab
2023-12-15  8:47 dpdklab
2023-12-15  8:47 dpdklab
2023-12-15  8:46 dpdklab
2023-12-15  8:45 dpdklab
2023-12-15  8:45 dpdklab
2023-12-15  8:42 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=657c1d3e.810a0220.e3b81.6810SMTPIN_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).