automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142399-142401 [PATCH] [3/3] examples/l3fwd: fix maximum
Date: Mon, 15 Jul 2024 04:07:46 -0700 (PDT)	[thread overview]
Message-ID: <66950302.050a0220.84d79.cc82SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240715101458.645014-3-g.singh@nxp.com>

Test-Label: iol-abi-testing
Test-Status: PENDING
http://dpdk.org/patch/142401

_Testing pending_

Submitter: Gagandeep Singh <g.singh@nxp.com>
Date: Monday, July 15 2024 10:14:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142399-142401 --> testing pending

Test environment and result as below:

+-------------------+----------+
|    Environment    | abi_test |
+===================+==========+
| RHEL8             | PEND     |
+-------------------+----------+
| CentOS Stream 8   | PASS     |
+-------------------+----------+
| Debian 12         | PEND     |
+-------------------+----------+
| CentOS Stream 9   | PEND     |
+-------------------+----------+
| Debian Bullseye   | PEND     |
+-------------------+----------+
| Fedora 37         | PASS     |
+-------------------+----------+
| Fedora 39 (Clang) | PASS     |
+-------------------+----------+
| Fedora 38 (Clang) | PASS     |
+-------------------+----------+
| Fedora 38         | PEND     |
+-------------------+----------+
| Fedora 39         | PEND     |
+-------------------+----------+
| Fedora 40 (Clang) | PEND     |
+-------------------+----------+
| openSUSE Leap 15  | PEND     |
+-------------------+----------+
| Fedora 40         | PEND     |
+-------------------+----------+
| RHEL9             | PASS     |
+-------------------+----------+
| Ubuntu 22.04      | PEND     |
+-------------------+----------+
| Ubuntu 24.04      | PEND     |
+-------------------+----------+


RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

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 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

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/30514/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-07-15 11:07 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240715101458.645014-3-g.singh@nxp.com>
2024-07-15  9:49 ` |SUCCESS| pw142399-142401 [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes qemudev
2024-07-15  9:53 ` qemudev
2024-07-15 10:16 ` |SUCCESS| pw142401 " checkpatch
2024-07-15 10:48 ` |PENDING| pw142399-142401 [PATCH] [3/3] examples/l3fwd: fix maximum dpdklab
2024-07-15 10:51 ` dpdklab
2024-07-15 10:51 ` |SUCCESS| " dpdklab
2024-07-15 10:55 ` |PENDING| " dpdklab
2024-07-15 10:57 ` |SUCCESS| " dpdklab
2024-07-15 10:58 ` |PENDING| " dpdklab
2024-07-15 10:58 ` dpdklab
2024-07-15 10:59 ` |SUCCESS| " dpdklab
2024-07-15 10:59 ` dpdklab
2024-07-15 10:59 ` |PENDING| " dpdklab
2024-07-15 10:59 ` |SUCCESS| " dpdklab
2024-07-15 11:00 ` |PENDING| " dpdklab
2024-07-15 11:02 ` dpdklab
2024-07-15 11:02 ` dpdklab
2024-07-15 11:03 ` |FAILURE| " dpdklab
2024-07-15 11:03 ` |SUCCESS| pw142401 [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes 0-day Robot
2024-07-15 11:03 ` |FAILURE| pw142399-142401 [PATCH] [3/3] examples/l3fwd: fix maximum dpdklab
2024-07-15 11:06 ` |PENDING| " dpdklab
2024-07-15 11:06 ` |FAILURE| " dpdklab
2024-07-15 11:06 ` |PENDING| " dpdklab
2024-07-15 11:06 ` dpdklab
2024-07-15 11:07 ` dpdklab [this message]
2024-07-15 11:10 ` |SUCCESS| " dpdklab
2024-07-15 11:11 ` |PENDING| " dpdklab
2024-07-15 11:12 ` |FAILURE| " dpdklab
2024-07-15 11:13 ` dpdklab
2024-07-15 11:13 ` |SUCCESS| " dpdklab
2024-07-15 11:14 ` |PENDING| " dpdklab
2024-07-15 11:15 ` dpdklab
2024-07-15 11:15 ` dpdklab
2024-07-15 11:15 ` dpdklab
2024-07-15 11:16 ` |SUCCESS| " dpdklab
2024-07-15 11:16 ` |FAILURE| " dpdklab
2024-07-15 11:17 ` |PENDING| " dpdklab
2024-07-15 11:17 ` dpdklab
2024-07-15 11:18 ` dpdklab
2024-07-15 11:21 ` dpdklab
2024-07-15 11:22 ` |FAILURE| " dpdklab
2024-07-15 11:22 ` |PENDING| " dpdklab
2024-07-15 11:22 ` dpdklab
2024-07-15 11:22 ` dpdklab
2024-07-15 11:23 ` |FAILURE| " dpdklab
2024-07-15 11:23 ` |SUCCESS| " dpdklab
2024-07-15 11:23 ` |PENDING| " dpdklab
2024-07-15 11:24 ` dpdklab
2024-07-15 11:24 ` dpdklab
2024-07-15 11:24 ` dpdklab
2024-07-15 11:25 ` dpdklab
2024-07-15 11:26 ` dpdklab
2024-07-15 11:27 ` dpdklab
2024-07-15 11:27 ` dpdklab
2024-07-15 11:27 ` dpdklab
2024-07-15 11:27 ` |FAILURE| " dpdklab
2024-07-15 11:27 ` |PENDING| " dpdklab
2024-07-15 11:28 ` dpdklab
2024-07-15 11:28 ` dpdklab
2024-07-15 11:29 ` dpdklab
2024-07-15 11:29 ` dpdklab
2024-07-15 11:30 ` dpdklab
2024-07-15 11:31 ` dpdklab
2024-07-15 11:32 ` dpdklab
2024-07-15 11:32 ` dpdklab
2024-07-15 11:32 ` dpdklab
2024-07-15 11:34 ` dpdklab
2024-07-15 11:34 ` |SUCCESS| " dpdklab
2024-07-15 11:34 ` |PENDING| " dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:36 ` dpdklab
2024-07-15 11:37 ` dpdklab
2024-07-15 11:37 ` |SUCCESS| " dpdklab
2024-07-15 11:37 ` dpdklab
2024-07-15 11:37 ` |PENDING| " dpdklab
2024-07-15 11:38 ` |FAILURE| " dpdklab
2024-07-15 11:39 ` dpdklab
2024-07-15 11:40 ` |PENDING| " dpdklab
2024-07-15 11:41 ` |FAILURE| " dpdklab
2024-07-15 11:43 ` dpdklab
2024-07-15 11:44 ` dpdklab
2024-07-15 11:44 ` |PENDING| " dpdklab
2024-07-15 11:45 ` |FAILURE| " dpdklab
2024-07-15 11:46 ` |PENDING| " dpdklab
2024-07-15 11:46 ` |FAILURE| " dpdklab
2024-07-15 11:47 ` |PENDING| " dpdklab
2024-07-15 11:48 ` dpdklab
2024-07-15 11:52 ` |FAILURE| " dpdklab
2024-07-15 11:54 ` |PENDING| " dpdklab
2024-07-15 11:56 ` dpdklab
2024-07-15 11:57 ` dpdklab
2024-07-15 11:57 ` |FAILURE| " dpdklab
2024-07-15 11:57 ` |PENDING| " dpdklab
2024-07-15 12:00 ` dpdklab
2024-07-15 12:00 ` |FAILURE| " dpdklab
2024-07-15 12:04 ` |PENDING| " dpdklab
2024-07-15 12:05 ` dpdklab
2024-07-15 12:16 ` |SUCCESS| " dpdklab
2024-07-15 12:17 ` |PENDING| " dpdklab
2024-07-15 12:28 ` dpdklab
2024-07-15 12:36 ` dpdklab
2024-07-15 12:54 ` |SUCCESS| " dpdklab
2024-07-15 12:55 ` dpdklab
2024-07-16  7:08 ` dpdklab
2024-07-16  7:12 ` dpdklab
2024-07-16  7:16 ` dpdklab
2024-07-16  7:20 ` dpdklab
2024-07-16  7:41 ` 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=66950302.050a0220.84d79.cc82SMTPIN_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).