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| pw139786-139794 [PATCH] [v11,9/9] net/tap: update document
Date: Wed, 01 May 2024 20:42:54 -0700 (PDT)	[thread overview]
Message-ID: <66330bbe.d40a0220.42d2d.0860SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240502025201.28322-10-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, May 02 2024 02:49:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139786-139794 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| CentOS Stream 9 | PASS     |
+-----------------+----------+
| Debian Bullseye | PASS     |
+-----------------+----------+
| Fedora 38       | PASS     |
+-----------------+----------+


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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-02  3:42 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240502025201.28322-10-stephen@networkplumber.org>
2024-05-02  2:28 ` |SUCCESS| pw139786-139794 [PATCH v11 9/9] net/tap: update documentation qemudev
2024-05-02  2:33 ` qemudev
2024-05-02  3:40 ` |SUCCESS| pw139786-139794 [PATCH] [v11,9/9] net/tap: update document dpdklab
2024-05-02  3:41 ` dpdklab
2024-05-02  3:41 ` dpdklab
2024-05-02  3:41 ` dpdklab
2024-05-02  3:42 ` dpdklab
2024-05-02  3:42 ` dpdklab
2024-05-02  3:42 ` dpdklab
2024-05-02  3:42 ` dpdklab
2024-05-02  3:42 ` dpdklab [this message]
2024-05-02  3:43 ` dpdklab
2024-05-02  3:43 ` dpdklab
2024-05-02  3:43 ` dpdklab
2024-05-02  3:43 ` dpdklab
2024-05-02  3:43 ` |SUCCESS| pw139794 [PATCH v11 9/9] net/tap: update documentation 0-day Robot
2024-05-02  3:43 ` |SUCCESS| pw139786-139794 [PATCH] [v11,9/9] net/tap: update document dpdklab
2024-05-02  3:44 ` dpdklab
2024-05-02  3:44 ` dpdklab
2024-05-02  3:45 ` dpdklab
2024-05-02  3:45 ` dpdklab
2024-05-02  3:45 ` dpdklab
2024-05-02  3:45 ` dpdklab
2024-05-02  3:45 ` dpdklab
2024-05-02  3:46 ` dpdklab
2024-05-02  3:46 ` dpdklab
2024-05-02  3:51 ` dpdklab
2024-05-02  3:51 ` dpdklab
2024-05-02  3:51 ` dpdklab
2024-05-02  3:51 ` dpdklab
2024-05-02  3:51 ` dpdklab
2024-05-02  3:52 ` dpdklab
2024-05-02  3:52 ` dpdklab
2024-05-02  3:52 ` dpdklab
2024-05-02  3:52 ` dpdklab
2024-05-02  3:52 ` dpdklab
2024-05-02  3:52 ` dpdklab
2024-05-02  3:53 ` dpdklab
2024-05-02  3:53 ` dpdklab
2024-05-02  3:53 ` dpdklab
2024-05-02  3:53 ` dpdklab
2024-05-02  3:55 ` dpdklab
2024-05-02  3:56 ` dpdklab
2024-05-02  3:56 ` dpdklab
2024-05-02  3:56 ` dpdklab
2024-05-02  3:56 ` dpdklab
2024-05-02  3:56 ` dpdklab
2024-05-02  3:57 ` dpdklab
2024-05-02  3:57 ` dpdklab
2024-05-02  3:57 ` dpdklab
2024-05-02  3:57 ` dpdklab
2024-05-02  3:58 ` dpdklab
2024-05-02  3:58 ` dpdklab
2024-05-02  3:58 ` dpdklab
2024-05-02  3:58 ` dpdklab
2024-05-02  3:58 ` dpdklab
2024-05-02  3:58 ` dpdklab
2024-05-02  3:59 ` dpdklab
2024-05-02  3:59 ` dpdklab
2024-05-02  3:59 ` dpdklab
2024-05-02  4:00 ` dpdklab
2024-05-02  4:00 ` dpdklab
2024-05-02  4:01 ` dpdklab
2024-05-02  4:01 ` dpdklab
2024-05-02  4:01 ` dpdklab
2024-05-02  4:01 ` dpdklab
2024-05-02  4:01 ` dpdklab
2024-05-02  4:02 ` dpdklab
2024-05-02  4:17 ` dpdklab
2024-05-02  4:19 ` dpdklab
2024-05-02  4:26 ` dpdklab
2024-05-02  4:30 ` dpdklab
2024-05-02  4:30 ` dpdklab
2024-05-02  4:31 ` dpdklab
2024-05-02  4:32 ` dpdklab
2024-05-02  4:32 ` dpdklab
2024-05-02  4:39 ` dpdklab
2024-05-02  4:41 ` dpdklab
2024-05-02  4:45 ` dpdklab
2024-05-02  5:14 ` dpdklab
2024-05-02  5:23 ` dpdklab
2024-05-04  2:11 ` dpdklab
2024-05-04 16:57 ` dpdklab
2024-05-04 17:01 ` dpdklab
2024-05-04 17:05 ` dpdklab
2024-05-04 17:10 ` dpdklab
2024-05-04 17:29 ` dpdklab
2024-05-06  6:51 ` 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=66330bbe.d40a0220.42d2d.0860SMTPIN_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).