From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: |SUCCESS| pw129111 [PATCH] doc: ensure sphinx output is reproducible
Date: Thu, 29 Jun 2023 06:45:52 -0700 (PDT) [thread overview]
Message-ID: <649d8b10.920a0220.3cdc2.9cdfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129111
_Testing PASS_
Submitter: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date: Thursday, June 29 2023 12:58:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:93a4b3beba4ee611685148917981f846427cafb2
129111 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Bullseye | 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: gcc 13.1.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.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/26864/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-29 13:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 13:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-30 23:33 dpdklab
2023-06-30 0:21 dpdklab
2023-06-30 0:05 dpdklab
2023-06-30 0:00 dpdklab
2023-06-29 23:56 dpdklab
2023-06-29 23:45 dpdklab
2023-06-29 14:58 dpdklab
2023-06-29 14:36 dpdklab
2023-06-29 14:26 dpdklab
2023-06-29 14:26 dpdklab
2023-06-29 14:26 dpdklab
2023-06-29 14:23 dpdklab
[not found] <20230629125838.1995751-1-christian.ehrhardt@canonical.com>
2023-06-29 12:46 ` qemudev
2023-06-29 12:50 ` qemudev
2023-06-29 13:00 ` checkpatch
2023-06-29 14:19 ` 0-day Robot
2023-06-29 14:19 dpdklab
2023-06-29 14:06 dpdklab
2023-06-29 14:03 dpdklab
2023-06-29 13:58 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:46 dpdklab
2023-06-29 13:45 dpdklab
2023-06-29 13:45 dpdklab
2023-06-29 13:45 dpdklab
2023-06-29 13:44 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=649d8b10.920a0220.3cdc2.9cdfSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=christian.ehrhardt@canonical.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).