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| pw136636 [PATCH] [V2] examples/pipeline: simplify the L2 f
Date: Tue, 13 Feb 2024 05:14:28 -0800 (PST)	[thread overview]
Message-ID: <65cb6b34.170a0220.75725.05f8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Date: Tuesday, February 13 2024 12:19:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:74fff67a34a33c8e6565cfbcb5618c268eb388c6

136636 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| Debian Buster    | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| Fedora 38        | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+


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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

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

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-13 13:14 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 13:14 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-13 15:01 dpdklab
2024-02-13 14:42 dpdklab
2024-02-13 14:29 dpdklab
2024-02-13 14:22 dpdklab
2024-02-13 14:14 dpdklab
2024-02-13 14:00 dpdklab
2024-02-13 13:58 dpdklab
2024-02-13 13:58 dpdklab
2024-02-13 13:57 dpdklab
2024-02-13 13:55 dpdklab
2024-02-13 13:54 dpdklab
2024-02-13 13:54 dpdklab
2024-02-13 13:53 dpdklab
2024-02-13 13:52 dpdklab
2024-02-13 13:52 dpdklab
2024-02-13 13:51 dpdklab
2024-02-13 13:50 dpdklab
2024-02-13 13:50 dpdklab
2024-02-13 13:48 dpdklab
2024-02-13 13:46 dpdklab
2024-02-13 13:46 dpdklab
2024-02-13 13:45 dpdklab
2024-02-13 13:45 dpdklab
2024-02-13 13:43 dpdklab
2024-02-13 13:43 dpdklab
2024-02-13 13:43 dpdklab
2024-02-13 13:38 dpdklab
2024-02-13 13:37 dpdklab
2024-02-13 13:31 dpdklab
2024-02-13 13:31 dpdklab
2024-02-13 13:29 dpdklab
2024-02-13 13:29 dpdklab
2024-02-13 13:29 dpdklab
2024-02-13 13:28 dpdklab
2024-02-13 13:28 dpdklab
2024-02-13 13:27 dpdklab
2024-02-13 13:27 dpdklab
2024-02-13 13:26 dpdklab
2024-02-13 13:26 dpdklab
2024-02-13 13:26 dpdklab
2024-02-13 13:25 dpdklab
2024-02-13 13:25 dpdklab
2024-02-13 13:25 dpdklab
2024-02-13 13:24 dpdklab
2024-02-13 13:24 dpdklab
2024-02-13 13:23 dpdklab
2024-02-13 13:23 dpdklab
2024-02-13 13:23 dpdklab
2024-02-13 13:23 dpdklab
2024-02-13 13:22 dpdklab
2024-02-13 13:21 dpdklab
2024-02-13 13:21 dpdklab
2024-02-13 13:21 dpdklab
2024-02-13 13:18 dpdklab
2024-02-13 13:18 dpdklab
2024-02-13 13:18 dpdklab
2024-02-13 13:18 dpdklab
2024-02-13 13:17 dpdklab
2024-02-13 13:17 dpdklab
2024-02-13 13:17 dpdklab
2024-02-13 13:17 dpdklab
2024-02-13 13:16 dpdklab
2024-02-13 13:16 dpdklab
2024-02-13 13:15 dpdklab
2024-02-13 13:15 dpdklab
2024-02-13 13:15 dpdklab
2024-02-13 13:14 dpdklab
2024-02-13 13:14 dpdklab
2024-02-13 13:13 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=65cb6b34.170a0220.75725.05f8SMTPIN_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).