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: |SUCCESS| pw136070-136076 [PATCH] [v2,7/7] net/gve: update GVE docum
Date: Tue, 23 Jan 2024 12:08:37 -0800 (PST)	[thread overview]
Message-ID: <65b01cc5.810a0220.3c2e1.cf38SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136076

_Testing PASS_

Submitter: Joshua Washington <joshwash@google.com>
Date: Tuesday, January 23 2024 17:58:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1b593b0c092a0e905cb1c05ba01acb6690fb0db2

136070-136076 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| Debian Buster    | PASS     |
+------------------+----------+
| Fedora 38        | PASS     |
+------------------+----------+
| Fedora 37        | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+


CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-23 20:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 20:08 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-24  4:27 dpdklab
2024-01-24  4:12 dpdklab
2024-01-23 21:14 dpdklab
2024-01-23 20:57 dpdklab
2024-01-23 20:18 dpdklab
2024-01-23 20:14 dpdklab
2024-01-23 20:14 dpdklab
2024-01-23 20:13 dpdklab
2024-01-23 20:08 dpdklab
2024-01-23 20:07 dpdklab
2024-01-23 20:06 dpdklab
2024-01-23 20:06 dpdklab
2024-01-23 20:04 dpdklab
2024-01-23 20:01 dpdklab
2024-01-23 19:59 dpdklab
2024-01-23 19:56 dpdklab
2024-01-23 19:55 dpdklab
2024-01-23 19:54 dpdklab
2024-01-23 19:51 dpdklab
2024-01-23 19:48 dpdklab
2024-01-23 19:48 dpdklab
2024-01-23 19:44 dpdklab
2024-01-23 19:44 dpdklab
2024-01-23 19:42 dpdklab
2024-01-23 19:41 dpdklab
2024-01-23 19:40 dpdklab
2024-01-23 19:39 dpdklab
2024-01-23 19:37 dpdklab
2024-01-23 19:36 dpdklab
2024-01-23 19:36 dpdklab
2024-01-23 19:29 dpdklab
2024-01-23 19:29 dpdklab
2024-01-23 19:28 dpdklab
2024-01-23 19:26 dpdklab
2024-01-23 19:25 dpdklab
2024-01-23 19:24 dpdklab
2024-01-23 19:21 dpdklab
2024-01-23 19:21 dpdklab
2024-01-23 19:09 dpdklab
2024-01-23 19:06 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=65b01cc5.810a0220.3c2e1.cf38SMTPIN_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).