From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: David Marchand <david.marchand@redhat.com>
Subject: |SUCCESS| pw136237-136238 [PATCH] [2/2] app/graph: fix build reason
Date: Wed, 31 Jan 2024 10:37:43 -0800 (PST) [thread overview]
Message-ID: <65ba9377.c80a0220.9d74.166cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136238
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Wednesday, January 31 2024 17:45:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5eedf66ac0e5ce62cd333e523996c63a3c4c2c00
136237-136238 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Fedora 38 | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
| Debian Bullseye | PASS |
+-----------------+----------+
| RHEL8 | PASS |
+-----------------+----------+
| Debian Buster | PASS |
+-----------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29005/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-31 18:37 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 18:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-31 19:48 dpdklab
2024-01-31 19:43 dpdklab
2024-01-31 19:25 dpdklab
2024-01-31 19:21 dpdklab
2024-01-31 19:18 dpdklab
2024-01-31 19:17 dpdklab
2024-01-31 19:17 dpdklab
2024-01-31 19:14 dpdklab
2024-01-31 19:13 dpdklab
2024-01-31 19:08 dpdklab
2024-01-31 19:07 dpdklab
2024-01-31 19:07 dpdklab
2024-01-31 19:04 dpdklab
2024-01-31 19:04 dpdklab
2024-01-31 19:01 dpdklab
2024-01-31 19:01 dpdklab
2024-01-31 19:01 dpdklab
2024-01-31 18:57 dpdklab
2024-01-31 18:57 dpdklab
2024-01-31 18:56 dpdklab
2024-01-31 18:49 dpdklab
2024-01-31 18:43 dpdklab
2024-01-31 18:43 dpdklab
2024-01-31 18:43 dpdklab
2024-01-31 18:43 dpdklab
2024-01-31 18:42 dpdklab
2024-01-31 18:42 dpdklab
2024-01-31 18:42 dpdklab
2024-01-31 18:41 dpdklab
2024-01-31 18:41 dpdklab
2024-01-31 18:41 dpdklab
2024-01-31 18:41 dpdklab
2024-01-31 18:35 dpdklab
2024-01-31 18:35 dpdklab
2024-01-31 18:34 dpdklab
2024-01-31 18:34 dpdklab
2024-01-31 18:34 dpdklab
2024-01-31 18:33 dpdklab
2024-01-31 18:33 dpdklab
2024-01-31 18:32 dpdklab
2024-01-31 18:31 dpdklab
2024-01-31 18:31 dpdklab
2024-01-31 18:30 dpdklab
2024-01-31 18:30 dpdklab
2024-01-31 18:28 dpdklab
2024-01-31 18:27 dpdklab
2024-01-31 18:27 dpdklab
2024-01-31 18:27 dpdklab
2024-01-31 18:26 dpdklab
2024-01-31 18:26 dpdklab
2024-01-31 18:26 dpdklab
2024-01-31 18:25 dpdklab
2024-01-31 18:24 dpdklab
2024-01-31 18:23 dpdklab
2024-01-31 18:23 dpdklab
2024-01-31 18:22 dpdklab
2024-01-31 18:22 dpdklab
2024-01-31 18:22 dpdklab
2024-01-31 18:22 dpdklab
2024-01-31 18:22 dpdklab
2024-01-31 18:21 dpdklab
2024-01-31 18:21 dpdklab
2024-01-31 18:21 dpdklab
2024-01-31 18:20 dpdklab
2024-01-31 18:20 dpdklab
2024-01-31 18:20 dpdklab
2024-01-31 18:20 dpdklab
[not found] <20240131174552.2601531-2-david.marchand@redhat.com>
2024-01-31 17:33 ` |SUCCESS| pw136237-136238 [PATCH 2/2] " qemudev
2024-01-31 17:37 ` qemudev
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=65ba9377.c80a0220.9d74.166cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.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).