From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130403 [PATCH] [v4,1/2] devtools: add check on symbol ma
Date: Wed, 16 Aug 2023 03:17:22 -0700 (PDT) [thread overview]
Message-ID: <64dca232.6b0a0220.f1578.f5dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130403
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Wednesday, August 16 2023 07:16:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81
130403 --> testing pass
Test environment and result as below:
+-----------------+--------------------+
| Environment | dpdk_meson_compile |
+=================+====================+
| Debian Buster | PASS |
+-----------------+--------------------+
| FreeBSD 13 | PASS |
+-----------------+--------------------+
| RHEL8 | PASS |
+-----------------+--------------------+
| CentOS Stream 9 | PASS |
+-----------------+--------------------+
| Fedora 37 | PASS |
+-----------------+--------------------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.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)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27351/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-16 10:17 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 10:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-16 11:55 dpdklab
2023-08-16 11:37 dpdklab
2023-08-16 11:37 dpdklab
2023-08-16 11:32 dpdklab
2023-08-16 11:27 dpdklab
2023-08-16 11:23 dpdklab
2023-08-16 11:15 dpdklab
2023-08-16 11:08 dpdklab
2023-08-16 11:03 dpdklab
2023-08-16 11:03 dpdklab
2023-08-16 10:59 dpdklab
2023-08-16 10:57 dpdklab
2023-08-16 10:55 dpdklab
2023-08-16 10:53 dpdklab
2023-08-16 10:53 dpdklab
2023-08-16 10:52 dpdklab
2023-08-16 10:51 dpdklab
2023-08-16 10:49 dpdklab
2023-08-16 10:47 dpdklab
2023-08-16 10:46 dpdklab
2023-08-16 10:46 dpdklab
2023-08-16 10:39 dpdklab
2023-08-16 10:38 dpdklab
2023-08-16 10:34 dpdklab
2023-08-16 10:34 dpdklab
2023-08-16 10:33 dpdklab
2023-08-16 10:32 dpdklab
2023-08-16 10:31 dpdklab
2023-08-16 10:29 dpdklab
2023-08-16 10:26 dpdklab
2023-08-16 10:25 dpdklab
2023-08-16 10:25 dpdklab
2023-08-16 10:25 dpdklab
2023-08-16 10:24 dpdklab
2023-08-16 10:23 dpdklab
2023-08-16 10:23 dpdklab
2023-08-16 10:23 dpdklab
2023-08-16 10:22 dpdklab
2023-08-16 10:22 dpdklab
2023-08-16 10:22 dpdklab
2023-08-16 10:21 dpdklab
2023-08-16 10:21 dpdklab
2023-08-16 10:20 dpdklab
2023-08-16 10:20 dpdklab
2023-08-16 10:20 dpdklab
2023-08-16 10:19 dpdklab
2023-08-16 10:19 dpdklab
2023-08-16 10:18 dpdklab
2023-08-16 10:17 dpdklab
2023-08-16 10:16 dpdklab
2023-08-16 10:16 dpdklab
2023-08-16 10:15 dpdklab
2023-08-16 10:15 dpdklab
2023-08-16 10:15 dpdklab
2023-08-16 10:15 dpdklab
2023-08-16 10:14 dpdklab
2023-08-16 10:14 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=64dca232.6b0a0220.f1578.f5dfSMTPIN_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).