From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136651 [PATCH] [V2] examples/pipeline: fix include path
Date: Wed, 14 Feb 2024 01:05:29 -0800 (PST) [thread overview]
Message-ID: <65cc8259.020a0220.dd9c4.0097SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136651
_Testing PASS_
Submitter: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Date: Tuesday, February 13 2024 17:38:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4cf59bbc9edf5419a9f2644a132c9a96c071a4c8
136651 --> testing pass
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+==============+======================+======================+
| Ubuntu 22.04 | PASS | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED | PASS |
+--------------+----------------------+----------------------+
Ubuntu 22.04
Kernel: 5.15.0-91-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29137/
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 9:05 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 9:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 7:55 dpdklab
2024-02-14 7:06 dpdklab
2024-02-14 5:52 dpdklab
2024-02-14 5:33 dpdklab
2024-02-14 5:03 dpdklab
2024-02-14 4:00 dpdklab
2024-02-14 3:49 dpdklab
2024-02-14 3:49 dpdklab
2024-02-14 3:43 dpdklab
2024-02-14 3:32 dpdklab
2024-02-14 3:29 dpdklab
2024-02-14 3:28 dpdklab
2024-02-14 3:28 dpdklab
2024-02-14 3:27 dpdklab
2024-02-14 3:26 dpdklab
2024-02-14 3:24 dpdklab
2024-02-14 3:23 dpdklab
2024-02-14 3:23 dpdklab
2024-02-14 3:21 dpdklab
2024-02-14 3:21 dpdklab
2024-02-14 3:20 dpdklab
2024-02-14 3:20 dpdklab
2024-02-14 3:19 dpdklab
2024-02-14 3:18 dpdklab
2024-02-14 3:14 dpdklab
2024-02-14 3:12 dpdklab
2024-02-14 3:10 dpdklab
2024-02-14 3:10 dpdklab
2024-02-14 3:10 dpdklab
2024-02-14 3:09 dpdklab
2024-02-14 3:09 dpdklab
2024-02-14 3:09 dpdklab
2024-02-14 3:08 dpdklab
2024-02-14 3:04 dpdklab
2024-02-14 3:00 dpdklab
2024-02-14 2:59 dpdklab
2024-02-14 2:57 dpdklab
2024-02-14 2:57 dpdklab
2024-02-14 2:56 dpdklab
2024-02-14 2:56 dpdklab
2024-02-14 2:56 dpdklab
2024-02-14 2:55 dpdklab
2024-02-14 2:50 dpdklab
2024-02-14 2:48 dpdklab
2024-02-14 2:46 dpdklab
2024-02-14 2:45 dpdklab
2024-02-14 2:45 dpdklab
2024-02-14 2:45 dpdklab
2024-02-14 2:42 dpdklab
2024-02-14 2:42 dpdklab
2024-02-14 2:41 dpdklab
2024-02-14 2:41 dpdklab
2024-02-14 2:40 dpdklab
2024-02-14 2:39 dpdklab
2024-02-14 2:37 dpdklab
2024-02-14 2:31 dpdklab
2024-02-14 2:31 dpdklab
2024-02-14 2:29 dpdklab
2024-02-14 2:29 dpdklab
2024-02-14 2:28 dpdklab
2024-02-14 2:27 dpdklab
2024-02-14 2:26 dpdklab
2024-02-14 2:26 dpdklab
2024-02-14 2:26 dpdklab
2024-02-14 2:25 dpdklab
2024-02-14 1:58 dpdklab
2024-02-14 1:58 dpdklab
2024-02-14 1:57 dpdklab
2024-02-14 1:57 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=65cc8259.020a0220.dd9c4.0097SMTPIN_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).