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| [GIT MASTER] d20fd65f258afb5b572fe686b7d1032aeb95e079
Date: Fri, 01 Nov 2024 02:26:25 -0700 (PDT)	[thread overview]
Message-ID: <67249ec1.050a0220.15c24e.5bb0SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v21.11

d20fd65f258afb5b572fe686b7d1032aeb95e079 --> testing pending

Upstream job id: Generic-DPDK-Compile-ABI#106183

Test environment and result as below:

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


CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

openSUSE Leap 15
	Kernel: Depends on container host
	Compiler: gcc (SUSE Linux) 7.5.0

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31393/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-01  9:26 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01  9:26 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-01 13:04 dpdklab
2024-11-01 12:49 dpdklab
2024-10-27  7:49 dpdklab
2024-10-26  7:23 dpdklab
2024-10-26  5:35 dpdklab
2024-10-25  6:35 dpdklab
2024-10-18 20:45 dpdklab
2024-10-18 20:27 dpdklab
2024-10-18 20:13 dpdklab
2024-10-18 19:51 dpdklab
2024-10-18  9:28 dpdklab
2024-10-16 23:05 dpdklab
2024-10-16 21:35 dpdklab
2024-10-16 20:55 dpdklab
2024-10-16 20:18 dpdklab
2024-10-16  7:12 dpdklab
2024-10-14 13:39 dpdklab
2024-10-14 12:53 dpdklab
2024-10-14 12:13 dpdklab
2024-10-13 10:46 dpdklab
2024-10-13  6:31 dpdklab
2024-10-11 16:55 dpdklab
2024-10-11 12:05 dpdklab
2024-10-11  6:29 dpdklab
2024-10-11  5:42 dpdklab
2024-10-11  5:17 dpdklab
2024-10-10  5:37 dpdklab
2024-10-10  5:09 dpdklab
2024-10-10  4:58 dpdklab
2024-10-09  8:27 dpdklab
2024-10-09  7:33 dpdklab
2024-10-09  6:08 dpdklab
2024-10-08  6:32 dpdklab
2024-10-08  4:43 dpdklab
2024-10-07  6:20 dpdklab
2024-10-07  5:28 dpdklab
2024-10-07  5:16 dpdklab
2024-10-07  5:12 dpdklab
2024-10-07  5:12 dpdklab
2024-10-06  8:26 dpdklab
2024-10-06  6:05 dpdklab
2024-10-06  5:08 dpdklab
2024-10-05  6:23 dpdklab
2024-10-05  6:19 dpdklab
2024-10-05  6:04 dpdklab
2024-10-05  5:20 dpdklab
2024-10-04 11:34 dpdklab
2024-10-04  8:30 dpdklab
2024-10-04  7:56 dpdklab
2024-10-04  7:39 dpdklab
2024-10-04  6:38 dpdklab
2024-10-03  6:08 dpdklab
2024-10-03  5:49 dpdklab
2024-10-03  5:14 dpdklab
2024-10-01  7:41 dpdklab
2024-10-01  6:26 dpdklab
2024-10-01  5:35 dpdklab
2024-10-01  5:22 dpdklab
2024-09-30  7:35 dpdklab
2024-09-30  5:57 dpdklab
2024-09-30  5:50 dpdklab
2024-09-30  5:32 dpdklab
2024-09-30  5:10 dpdklab
2024-09-29  5:37 dpdklab
2024-09-29  4:53 dpdklab
2024-09-29  4:50 dpdklab
2024-09-28  6:00 dpdklab
2024-09-28  5:45 dpdklab
2024-09-28  5:37 dpdklab
2024-09-28  4:17 dpdklab
2024-09-27 10:24 dpdklab
2024-09-27  8:33 dpdklab
2024-09-27  6:42 dpdklab
2024-09-26 11:43 dpdklab
2024-09-26 11:00 dpdklab
2024-09-26 10:47 dpdklab
2024-09-26  7:56 dpdklab
2024-09-26  6:23 dpdklab
2024-09-25  6:29 dpdklab
2024-09-25  5:53 dpdklab
2024-09-25  5:04 dpdklab
2024-09-24  6:21 dpdklab
2024-09-24  5:43 dpdklab
2024-09-24  5:30 dpdklab
2024-09-24  4:20 dpdklab
2024-09-23  8:15 dpdklab
2024-09-23  5:41 dpdklab
2024-09-23  5:26 dpdklab
2024-09-23  4:44 dpdklab
2024-09-22  5:48 dpdklab
2024-09-22  5:38 dpdklab
2024-09-22  5:29 dpdklab
2024-09-22  4:55 dpdklab
2024-09-21  5:49 dpdklab
2024-09-21  5:43 dpdklab
2024-09-21  4:43 dpdklab
2024-09-20  7:11 dpdklab
2024-09-20  6:22 dpdklab
2024-09-20  6:04 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=67249ec1.050a0220.15c24e.5bb0SMTPIN_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).