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| pw138115 [PATCH] net/nfp: fix failure of PF initiation on
Date: Thu, 07 Mar 2024 20:04:05 -0800 (PST)	[thread overview]
Message-ID: <65ea8e35.050a0220.659d3.921cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240308031110.2041280-1-chaoyong.he@corigine.com>

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

_Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, March 08 2024 03:11:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7fcf4e8a03c4b0d2c6cec11ddd18c7bf88ba0384

138115 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Fedora 38        | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+


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

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

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/29470/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-08  4:04 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240308031110.2041280-1-chaoyong.he@corigine.com>
2024-03-08  2:49 ` |SUCCESS| pw138115 [PATCH] net/nfp: fix failure of PF initiation on flower firmware qemudev
2024-03-08  2:54 ` qemudev
2024-03-08  3:11 ` checkpatch
2024-03-08  3:48 ` |SUCCESS| pw138115 [PATCH] net/nfp: fix failure of PF initiation on dpdklab
2024-03-08  3:48 ` dpdklab
2024-03-08  3:49 ` dpdklab
2024-03-08  3:50 ` dpdklab
2024-03-08  3:50 ` dpdklab
2024-03-08  3:50 ` dpdklab
2024-03-08  3:51 ` dpdklab
2024-03-08  3:51 ` dpdklab
2024-03-08  3:51 ` dpdklab
2024-03-08  3:52 ` dpdklab
2024-03-08  3:52 ` dpdklab
2024-03-08  3:52 ` dpdklab
2024-03-08  3:53 ` dpdklab
2024-03-08  3:55 ` dpdklab
2024-03-08  3:55 ` dpdklab
2024-03-08  3:56 ` dpdklab
2024-03-08  3:56 ` dpdklab
2024-03-08  3:56 ` dpdklab
2024-03-08  3:56 ` dpdklab
2024-03-08  3:56 ` dpdklab
2024-03-08  3:57 ` dpdklab
2024-03-08  3:58 ` dpdklab
2024-03-08  3:58 ` dpdklab
2024-03-08  3:58 ` dpdklab
2024-03-08  3:59 ` dpdklab
2024-03-08  4:00 ` dpdklab
2024-03-08  4:01 ` dpdklab
2024-03-08  4:01 ` dpdklab
2024-03-08  4:02 ` dpdklab
2024-03-08  4:02 ` dpdklab
2024-03-08  4:02 ` dpdklab
2024-03-08  4:03 ` dpdklab
2024-03-08  4:03 ` dpdklab
2024-03-08  4:03 ` dpdklab
2024-03-08  4:04 ` dpdklab [this message]
2024-03-08  4:04 ` |SUCCESS| pw138115 [PATCH] net/nfp: fix failure of PF initiation on flower firmware 0-day Robot
2024-03-08  4:04 ` |SUCCESS| pw138115 [PATCH] net/nfp: fix failure of PF initiation on dpdklab
2024-03-08  4:06 ` dpdklab
2024-03-08  4:06 ` dpdklab
2024-03-08  4:06 ` dpdklab
2024-03-08  4:07 ` dpdklab
2024-03-08  4:08 ` dpdklab
2024-03-08  4:08 ` dpdklab
2024-03-08  4:08 ` dpdklab
2024-03-08  4:09 ` dpdklab
2024-03-08  4:09 ` dpdklab
2024-03-08  4:10 ` dpdklab
2024-03-08  4:10 ` dpdklab
2024-03-08  4:10 ` dpdklab
2024-03-08  4:10 ` dpdklab
2024-03-08  4:11 ` dpdklab
2024-03-08  4:14 ` dpdklab
2024-03-08  4:14 ` dpdklab
2024-03-08  4:16 ` dpdklab
2024-03-08  4:16 ` dpdklab
2024-03-08  4:17 ` dpdklab
2024-03-08  4:18 ` dpdklab
2024-03-08  4:25 ` dpdklab
2024-03-08  4:25 ` dpdklab
2024-03-08  4:26 ` dpdklab
2024-03-08  4:28 ` dpdklab
2024-03-08  4:31 ` dpdklab
2024-03-08  4:34 ` dpdklab
2024-03-08  4:35 ` dpdklab
2024-03-08  4:39 ` dpdklab
2024-03-08  4:46 ` dpdklab
2024-03-08  7:11 ` dpdklab
2024-03-08 10:05 ` dpdklab
2024-03-08 10:09 ` dpdklab
2024-03-08 10:11 ` dpdklab
2024-03-08 10:13 ` dpdklab
2024-03-12 13:23 ` dpdklab
2024-03-12 13:59 ` 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=65ea8e35.050a0220.659d3.921cSMTPIN_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).