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| pw149308 [PATCH] net/gve: Allocate qpl pages using malloc
Date: Wed, 08 Jan 2025 01:07:09 -0800 (PST)	[thread overview]
Message-ID: <677e403d.050a0220.1ff02a.e2dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241218234635.2009033-1-joshwash@google.com>

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

_Testing pending_

Submitter: Joshua Washington <joshwash@google.com>
Date: Wednesday, December 18 2024 23:46:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:78d0246a2e2fb14cba220d507192d12d2ce896ac

149308 --> testing pending

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

Test environment and result as below:

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


CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

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

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

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

Fedora 41 (Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

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

Fedora 41
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

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

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.3.0-6ubuntu2~24.04) 13.3.0

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32163/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-01-08  9:07 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241218234635.2009033-1-joshwash@google.com>
2024-12-18 23:15 ` |SUCCESS| pw149308 [PATCH] net/gve: Allocate qpl pages using malloc if memzone allocation fails qemudev
2024-12-18 23:19 ` qemudev
2024-12-18 23:46 ` checkpatch
2024-12-19  0:43 ` |FAILURE| " 0-day Robot
2024-12-19  1:28 ` |SUCCESS| pw149308 [PATCH] net/gve: Allocate qpl pages using malloc dpdklab
2024-12-19  1:34 ` dpdklab
2024-12-19  1:36 ` dpdklab
2024-12-19  1:37 ` |PENDING| " dpdklab
2024-12-19  1:38 ` |SUCCESS| " dpdklab
2024-12-19  1:41 ` dpdklab
2024-12-19  1:42 ` dpdklab
2024-12-19  1:44 ` dpdklab
2024-12-19  1:46 ` dpdklab
2024-12-19  1:50 ` dpdklab
2024-12-19  1:51 ` dpdklab
2024-12-19  1:51 ` dpdklab
2024-12-19  1:59 ` dpdklab
2024-12-19  2:07 ` dpdklab
2024-12-19  2:08 ` dpdklab
2024-12-19  2:16 ` dpdklab
2024-12-19  2:20 ` dpdklab
2024-12-19  2:32 ` |FAILURE| " dpdklab
2024-12-19  2:32 ` dpdklab
2024-12-19  2:36 ` dpdklab
2024-12-19  2:38 ` dpdklab
2024-12-19  2:40 ` |SUCCESS| " dpdklab
2024-12-19  2:40 ` |FAILURE| " dpdklab
2024-12-19  2:41 ` dpdklab
2024-12-19  2:49 ` |SUCCESS| " dpdklab
2024-12-19  2:49 ` dpdklab
2024-12-19  2:50 ` dpdklab
2024-12-19  2:52 ` dpdklab
2024-12-19  2:52 ` |WARNING| " dpdklab
2024-12-19  2:53 ` dpdklab
2024-12-19  2:58 ` |SUCCESS| " dpdklab
2024-12-19  3:15 ` |FAILURE| " dpdklab
2024-12-19  3:15 ` dpdklab
2024-12-19  3:17 ` dpdklab
2024-12-19  3:17 ` dpdklab
2024-12-19  3:18 ` |SUCCESS| " dpdklab
2024-12-19  3:19 ` |FAILURE| " dpdklab
2024-12-19  3:21 ` dpdklab
2024-12-19  3:22 ` dpdklab
2024-12-19  3:22 ` |SUCCESS| " dpdklab
2024-12-19  3:25 ` |FAILURE| " dpdklab
2024-12-19  3:40 ` |SUCCESS| " dpdklab
2024-12-19  3:47 ` |WARNING| " dpdklab
2024-12-19  3:47 ` |FAILURE| " dpdklab
2024-12-19  4:14 ` dpdklab
2024-12-19  4:23 ` |SUCCESS| " dpdklab
2024-12-19  4:38 ` |WARNING| " dpdklab
2024-12-19  4:39 ` dpdklab
2024-12-19  4:43 ` dpdklab
2024-12-19  4:45 ` dpdklab
2024-12-19  5:00 ` |SUCCESS| " dpdklab
2024-12-19  5:29 ` |FAILURE| " dpdklab
2025-01-07  9:11 ` |WARNING| " dpdklab
2025-01-07 10:24 ` dpdklab
2025-01-07 10:40 ` dpdklab
2025-01-08  8:48 ` |PENDING| " dpdklab
2025-01-08  9:07 ` dpdklab [this message]
2025-01-08 10:05 ` |SUCCESS| " 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=677e403d.050a0220.1ff02a.e2dfSMTPIN_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).