From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124200 [PATCH] ipsec_mb: expect ENOTSUP in ipsec_mb_create()
Date: Mon, 20 Feb 2023 13:20:03 -0500 (EST) [thread overview]
Message-ID: <20230220182003.6FB4045F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124200
_Functional Testing PASS_
Submitter: Krzysztof Karas <krzysztof.karas@intel.com>
Date: Monday, February 20 2023 17:13:18
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fc6bdd5248e843ba1300c8d46d43b263b4a69438
124200 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25467/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-20 18:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 18:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 20:17 dpdklab
2023-02-21 0:13 dpdklab
2023-02-20 21:16 dpdklab
2023-02-20 21:15 dpdklab
2023-02-20 21:11 dpdklab
2023-02-20 21:09 dpdklab
2023-02-20 21:07 dpdklab
2023-02-20 21:07 dpdklab
2023-02-20 21:06 dpdklab
2023-02-20 21:04 dpdklab
2023-02-20 21:02 dpdklab
2023-02-20 21:01 dpdklab
2023-02-20 20:54 dpdklab
2023-02-20 20:52 dpdklab
2023-02-20 20:51 dpdklab
2023-02-20 20:13 dpdklab
2023-02-20 18:40 dpdklab
2023-02-20 18:33 dpdklab
2023-02-20 18:17 dpdklab
2023-02-20 18:05 dpdklab
2023-02-20 18:01 dpdklab
2023-02-20 17:53 dpdklab
2023-02-20 17:50 dpdklab
2023-02-20 17:49 dpdklab
2023-02-20 17:46 dpdklab
[not found] <20230220171318.1836477-1-krzysztof.karas@intel.com>
2023-02-20 17:07 ` qemudev
2023-02-20 17:11 ` qemudev
2023-02-20 19:19 ` 0-day Robot
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=20230220182003.6FB4045F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).