From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136650 [PATCH] [RFC] net/bonding: add user callback for
Date: Tue, 13 Feb 2024 19:11:03 -0800 (PST) [thread overview]
Message-ID: <65cc2f47.170a0220.f7071.1c30SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136650
_Testing PASS_
Submitter: Vignesh Purushotham Srinivas <vignesh.purushotham.srinivas@ericsson.com>
Date: Tuesday, February 13 2024 17:22:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4cf59bbc9edf5419a9f2644a132c9a96c071a4c8
136650 --> testing pass
Test environment and result as below:
+-----------------------+----------------+
| Environment | dpdk_unit_test |
+=======================+================+
| CentOS Stream 9 (ARM) | PASS |
+-----------------------+----------------+
| Fedora 37 (ARM) | PASS |
+-----------------------+----------------+
| Fedora 38 (ARM) | PASS |
+-----------------------+----------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29136/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-14 3:11 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 3:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 22:50 dpdklab
2024-02-14 9:35 dpdklab
2024-02-14 8:51 dpdklab
2024-02-14 8:21 dpdklab
2024-02-14 6:58 dpdklab
2024-02-14 6:51 dpdklab
2024-02-14 6:28 dpdklab
2024-02-14 5:58 dpdklab
2024-02-14 5:05 dpdklab
2024-02-14 4:41 dpdklab
2024-02-14 4:38 dpdklab
2024-02-14 4:32 dpdklab
2024-02-14 4:31 dpdklab
2024-02-14 4:29 dpdklab
2024-02-14 4:29 dpdklab
2024-02-14 4:28 dpdklab
2024-02-14 4:28 dpdklab
2024-02-14 4:27 dpdklab
2024-02-14 4:27 dpdklab
2024-02-14 4:27 dpdklab
2024-02-14 4:26 dpdklab
2024-02-14 4:26 dpdklab
2024-02-14 4:25 dpdklab
2024-02-14 4:15 dpdklab
2024-02-14 4:15 dpdklab
2024-02-14 4:15 dpdklab
2024-02-14 4:15 dpdklab
2024-02-14 4:14 dpdklab
2024-02-14 4:14 dpdklab
2024-02-14 4:07 dpdklab
2024-02-14 4:06 dpdklab
2024-02-14 4:05 dpdklab
2024-02-14 4:05 dpdklab
2024-02-14 4:05 dpdklab
2024-02-14 4:05 dpdklab
2024-02-14 4:04 dpdklab
2024-02-14 4:03 dpdklab
2024-02-14 4:03 dpdklab
2024-02-14 4:03 dpdklab
2024-02-14 4:02 dpdklab
2024-02-14 4:02 dpdklab
2024-02-14 4:01 dpdklab
2024-02-14 3:59 dpdklab
2024-02-14 3:58 dpdklab
2024-02-14 3:57 dpdklab
2024-02-14 3:51 dpdklab
2024-02-14 3:50 dpdklab
2024-02-14 3:46 dpdklab
2024-02-14 3:44 dpdklab
2024-02-14 3:35 dpdklab
2024-02-14 3:23 dpdklab
2024-02-14 3:18 dpdklab
2024-02-14 3:18 dpdklab
2024-02-14 3:16 dpdklab
2024-02-14 3:13 dpdklab
2024-02-14 3:11 dpdklab
2024-02-14 3:11 dpdklab
2024-02-14 3:10 dpdklab
2024-02-14 3:09 dpdklab
2024-02-14 3:08 dpdklab
2024-02-14 3:07 dpdklab
2024-02-14 3:06 dpdklab
2024-02-14 3:06 dpdklab
2024-02-14 3:05 dpdklab
2024-02-14 3:05 dpdklab
2024-02-14 3:00 dpdklab
2024-02-14 2:59 dpdklab
2024-02-14 2:55 dpdklab
2024-02-14 2:51 dpdklab
2024-02-14 2:50 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=65cc2f47.170a0220.f7071.1c30SMTPIN_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).