From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Amit Prakash Shukla <amitprakashs@marvell.com>
Subject: |SUCCESS| pw126914 [PATCH] [v8] mem: telemetry support for memseg and element information
Date: Wed, 17 May 2023 05:27:03 -0700 (PDT) [thread overview]
Message-ID: <6464c817.0c0a0220.6b913.2e36SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126914
_Testing PASS_
Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Wednesday, May 17 2023 09:21:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c
126914 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| RHEL 7 | PASS |
+-----------------+----------+
| Ubuntu 22.04 | PASS |
+-----------------+----------+
| Debian Bullseye | PASS |
+-----------------+----------+
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)
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26254/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-17 12:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 12:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-17 16:37 dpdklab
2023-05-17 16:37 dpdklab
2023-05-17 14:25 dpdklab
2023-05-17 14:08 dpdklab
[not found] <20230517092158.1679036-1-amitprakashs@marvell.com>
2023-05-17 9:12 ` |SUCCESS| pw126914 [PATCH v8] " qemudev
2023-05-17 9:16 ` qemudev
2023-05-17 9:23 ` checkpatch
2023-05-17 14:00 ` 0-day Robot
2023-05-17 13:16 |SUCCESS| pw126914 [PATCH] [v8] " dpdklab
2023-05-17 13:13 dpdklab
2023-05-17 13:13 dpdklab
2023-05-17 13:03 dpdklab
2023-05-17 12:59 dpdklab
2023-05-17 12:55 dpdklab
2023-05-17 12:53 dpdklab
2023-05-17 12:45 dpdklab
2023-05-17 12:31 dpdklab
2023-05-17 12:29 dpdklab
2023-05-17 12:25 dpdklab
2023-05-17 12:16 dpdklab
2023-05-17 11:36 dpdklab
2023-05-17 11:30 dpdklab
2023-05-17 11:27 dpdklab
2023-05-17 11:20 dpdklab
2023-05-17 11:20 dpdklab
2023-05-17 11:14 dpdklab
2023-05-17 11:14 dpdklab
2023-05-17 11:14 dpdklab
2023-05-17 11:13 dpdklab
2023-05-17 11:06 dpdklab
2023-05-17 11:05 dpdklab
2023-05-17 11:05 dpdklab
2023-05-17 11:01 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=6464c817.0c0a0220.6b913.2e36SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=amitprakashs@marvell.com \
--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).