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| pw136181 [PATCH] app/testpmd: support updating flow rule a
Date: Fri, 26 Jan 2024 06:10:30 -0800 (PST)	[thread overview]
Message-ID: <65b3bd56.170a0220.883ea.bfa8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Oleksandr Kolomeiets <okl-plv@napatech.com>
Date: Friday, January 26 2024 13:21:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6676a3793b4292baf606092a8e3e14ea67550c58

136181 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| RHEL8            | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+


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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-26 14:10 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 14:10 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-26 15:25 dpdklab
2024-01-26 15:19 dpdklab
2024-01-26 15:19 dpdklab
2024-01-26 15:19 dpdklab
2024-01-26 15:11 dpdklab
2024-01-26 15:10 dpdklab
2024-01-26 15:09 dpdklab
2024-01-26 15:06 dpdklab
2024-01-26 15:01 dpdklab
2024-01-26 15:00 dpdklab
2024-01-26 15:00 dpdklab
2024-01-26 14:57 dpdklab
2024-01-26 14:55 dpdklab
2024-01-26 14:55 dpdklab
2024-01-26 14:52 dpdklab
2024-01-26 14:48 dpdklab
2024-01-26 14:44 dpdklab
2024-01-26 14:43 dpdklab
2024-01-26 14:33 dpdklab
2024-01-26 14:28 dpdklab
2024-01-26 14:20 dpdklab
2024-01-26 14:17 dpdklab
2024-01-26 14:17 dpdklab
2024-01-26 14:14 dpdklab
2024-01-26 14:13 dpdklab
2024-01-26 14:13 dpdklab
2024-01-26 14:12 dpdklab
2024-01-26 14:12 dpdklab
2024-01-26 14:11 dpdklab
2024-01-26 14:11 dpdklab
2024-01-26 14:10 dpdklab
2024-01-26 14:10 dpdklab
2024-01-26 14:09 dpdklab
2024-01-26 14:08 dpdklab
2024-01-26 14:08 dpdklab
2024-01-26 14:08 dpdklab
2024-01-26 14:07 dpdklab
2024-01-26 14:07 dpdklab
2024-01-26 14:07 dpdklab
2024-01-26 14:06 dpdklab
2024-01-26 14:05 dpdklab
2024-01-26 14:05 dpdklab
2024-01-26 14:04 dpdklab
2024-01-26 14:04 dpdklab
2024-01-26 14:03 dpdklab
2024-01-26 14:03 dpdklab
2024-01-26 14:03 dpdklab
2024-01-26 14:03 dpdklab
2024-01-26 14:03 dpdklab
2024-01-26 14:02 dpdklab
2024-01-26 14:02 dpdklab
2024-01-26 14:02 dpdklab
2024-01-26 14:01 dpdklab
2024-01-26 14:01 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=65b3bd56.170a0220.883ea.bfa8SMTPIN_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).