From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw143049 [PATCH] net/bnxt: fix issue reading sff8436 sfp e
Date: Fri, 09 Aug 2024 07:37:55 -0700 (PDT) [thread overview]
Message-ID: <66b629c3.0d0a0220.154b1e.c60aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240809102115.629429-1-pdmorrow@gmail.com>
Test-Label: iol-abi-testing
Test-Status: PENDING
http://dpdk.org/patch/143049
_Testing pending_
Submitter: Peter Morrow <pdmorrow@gmail.com>
Date: Friday, August 09 2024 10:21:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3
143049 --> testing pending
Upstream job id: Generic-DPDK-Compile-ABI#102270
Test environment and result as below:
+-------------------+----------+
| Environment | abi_test |
+===================+==========+
| CentOS Stream 9 | PASS |
+-------------------+----------+
| Debian 12 | PEND |
+-------------------+----------+
| Debian Bullseye | PASS |
+-------------------+----------+
| Fedora 37 | PASS |
+-------------------+----------+
| Fedora 38 (Clang) | PASS |
+-------------------+----------+
| Fedora 38 | PEND |
+-------------------+----------+
| Fedora 40 | PEND |
+-------------------+----------+
| Fedora 40 (Clang) | PEND |
+-------------------+----------+
| Fedora 39 | PASS |
+-------------------+----------+
| openSUSE Leap 15 | PEND |
+-------------------+----------+
| Fedora 39 (Clang) | PEND |
+-------------------+----------+
| RHEL9 | PEND |
+-------------------+----------+
| Ubuntu 22.04 | PEND |
+-------------------+----------+
| Ubuntu 24.04 | PEND |
+-------------------+----------+
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.1.1
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30756/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-08-09 14:37 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240809102115.629429-1-pdmorrow@gmail.com>
2024-08-09 10:38 ` |SUCCESS| pw143049 [PATCH] net/bnxt: fix issue reading sff8436 sfp eeproms qemudev
2024-08-09 10:42 ` qemudev
2024-08-09 11:05 ` |WARNING| " checkpatch
2024-08-09 12:02 ` |SUCCESS| " 0-day Robot
2024-08-09 12:27 ` |SUCCESS| pw143049 [PATCH] net/bnxt: fix issue reading sff8436 sfp e dpdklab
2024-08-09 12:29 ` dpdklab
2024-08-09 12:30 ` |PENDING| " dpdklab
2024-08-09 12:31 ` |SUCCESS| " dpdklab
2024-08-09 12:35 ` dpdklab
2024-08-09 12:36 ` dpdklab
2024-08-09 12:38 ` dpdklab
2024-08-09 12:44 ` dpdklab
2024-08-09 12:48 ` dpdklab
2024-08-09 12:51 ` dpdklab
2024-08-09 12:51 ` dpdklab
2024-08-09 13:14 ` dpdklab
2024-08-09 13:47 ` dpdklab
2024-08-09 13:51 ` dpdklab
2024-08-09 13:56 ` dpdklab
2024-08-09 14:01 ` dpdklab
2024-08-09 14:19 ` |PENDING| " dpdklab
2024-08-09 14:21 ` |SUCCESS| " dpdklab
2024-08-09 14:31 ` |PENDING| " dpdklab
2024-08-09 14:37 ` dpdklab
2024-08-09 14:37 ` dpdklab [this message]
2024-08-09 14:40 ` dpdklab
2024-08-09 14:43 ` dpdklab
2024-08-09 14:47 ` dpdklab
2024-08-09 14:47 ` dpdklab
2024-08-09 14:49 ` dpdklab
2024-08-09 14:55 ` dpdklab
2024-08-09 15:03 ` dpdklab
2024-08-09 15:07 ` dpdklab
2024-08-09 15:07 ` dpdklab
2024-08-09 18:22 ` dpdklab
2024-08-09 18:25 ` dpdklab
2024-08-09 18:28 ` dpdklab
2024-08-09 18:29 ` dpdklab
2024-08-09 18:34 ` dpdklab
2024-08-09 18:47 ` dpdklab
2024-08-09 18:54 ` |FAILURE| " dpdklab
2024-08-09 18:56 ` dpdklab
2024-08-09 18:58 ` dpdklab
2024-08-09 18:59 ` dpdklab
2024-08-09 19:01 ` dpdklab
2024-08-09 19:01 ` dpdklab
2024-08-09 19:04 ` dpdklab
2024-08-09 19:09 ` |PENDING| " dpdklab
2024-08-09 19:16 ` dpdklab
2024-08-09 19:18 ` dpdklab
2024-08-09 19:18 ` dpdklab
2024-08-09 19:19 ` dpdklab
2024-08-09 19:21 ` dpdklab
2024-08-09 19:22 ` dpdklab
2024-08-09 19:23 ` dpdklab
2024-08-09 19:27 ` dpdklab
2024-08-09 19:28 ` dpdklab
2024-08-09 19:31 ` dpdklab
2024-08-09 19:34 ` dpdklab
2024-08-09 19:34 ` dpdklab
2024-08-09 19:37 ` |SUCCESS| " dpdklab
2024-08-09 19:40 ` |PENDING| " dpdklab
2024-08-09 19:41 ` dpdklab
2024-08-09 19:41 ` |FAILURE| " dpdklab
2024-08-09 19:42 ` |PENDING| " dpdklab
2024-08-09 19:48 ` dpdklab
2024-08-09 19:52 ` dpdklab
2024-08-09 19:54 ` dpdklab
2024-08-09 19:58 ` dpdklab
2024-08-09 20:05 ` dpdklab
2024-08-09 20:05 ` dpdklab
2024-08-09 20:18 ` dpdklab
2024-08-09 20:18 ` dpdklab
2024-08-09 20:19 ` dpdklab
2024-08-09 20:19 ` dpdklab
2024-08-09 20:20 ` dpdklab
2024-08-09 20:20 ` dpdklab
2024-08-09 20:20 ` dpdklab
2024-08-09 20:21 ` dpdklab
2024-08-09 20:21 ` dpdklab
2024-08-09 20:22 ` dpdklab
2024-08-09 20:26 ` dpdklab
2024-08-09 20:27 ` dpdklab
2024-08-09 20:28 ` dpdklab
2024-08-09 20:28 ` dpdklab
2024-08-09 20:33 ` dpdklab
2024-08-09 20:34 ` dpdklab
2024-08-09 20:42 ` dpdklab
2024-08-09 20:45 ` dpdklab
2024-08-09 21:07 ` dpdklab
2024-08-09 21:08 ` dpdklab
2024-08-09 21:09 ` dpdklab
2024-08-09 21:17 ` |SUCCESS| " dpdklab
2024-08-10 2:35 ` 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=66b629c3.0d0a0220.154b1e.c60aSMTPIN_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).