From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138003 [PATCH] [v3] config/arm: add Marvell Odyssey
Date: Sun, 10 Mar 2024 12:28:53 -0700 (PDT) [thread overview]
Message-ID: <65ee09f5.c80a0220.e8a9d.c6a0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240306055029.424-1-anoobj@marvell.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138003
_Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wednesday, March 06 2024 05:50:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7fcf4e8a03c4b0d2c6cec11ddd18c7bf88ba0384
138003 --> testing pass
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | PASS | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED | PASS |
+--------------+----------------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.15.0-91-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29426/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-03-10 19:28 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306055029.424-1-anoobj@marvell.com>
2024-03-06 5:27 ` |SUCCESS| pw138003 [PATCH v3] " qemudev
2024-03-06 5:32 ` qemudev
2024-03-06 5:52 ` checkpatch
2024-03-06 6:45 ` 0-day Robot
2024-03-06 7:06 ` |SUCCESS| pw138003 [PATCH] [v3] " dpdklab
2024-03-06 7:45 ` dpdklab
2024-03-06 7:45 ` dpdklab
2024-03-06 7:46 ` dpdklab
2024-03-06 7:47 ` dpdklab
2024-03-06 7:47 ` dpdklab
2024-03-06 7:47 ` dpdklab
2024-03-06 7:48 ` dpdklab
2024-03-06 7:48 ` dpdklab
2024-03-06 7:48 ` dpdklab
2024-03-06 7:49 ` dpdklab
2024-03-06 7:49 ` dpdklab
2024-03-06 7:51 ` dpdklab
2024-03-06 7:52 ` dpdklab
2024-03-06 7:53 ` dpdklab
2024-03-06 7:54 ` dpdklab
2024-03-06 7:54 ` dpdklab
2024-03-06 7:55 ` dpdklab
2024-03-06 7:55 ` dpdklab
2024-03-06 7:55 ` dpdklab
2024-03-06 7:56 ` dpdklab
2024-03-06 7:56 ` dpdklab
2024-03-06 7:57 ` dpdklab
2024-03-06 7:58 ` dpdklab
2024-03-06 8:02 ` dpdklab
2024-03-06 8:03 ` dpdklab
2024-03-06 8:05 ` dpdklab
2024-03-06 8:07 ` dpdklab
2024-03-06 8:07 ` dpdklab
2024-03-06 8:08 ` dpdklab
2024-03-06 8:08 ` dpdklab
2024-03-06 8:10 ` dpdklab
2024-03-06 8:11 ` dpdklab
2024-03-06 8:12 ` dpdklab
2024-03-06 8:13 ` dpdklab
2024-03-06 8:13 ` dpdklab
2024-03-06 8:13 ` dpdklab
2024-03-06 8:13 ` dpdklab
2024-03-06 8:15 ` dpdklab
2024-03-06 8:15 ` dpdklab
2024-03-06 8:16 ` dpdklab
2024-03-06 8:16 ` dpdklab
2024-03-06 8:16 ` dpdklab
2024-03-06 8:16 ` dpdklab
2024-03-06 8:17 ` dpdklab
2024-03-06 8:17 ` dpdklab
2024-03-06 8:18 ` dpdklab
2024-03-06 8:18 ` dpdklab
2024-03-06 8:19 ` dpdklab
2024-03-06 8:19 ` dpdklab
2024-03-06 8:19 ` dpdklab
2024-03-06 8:19 ` dpdklab
2024-03-06 8:20 ` dpdklab
2024-03-06 8:22 ` dpdklab
2024-03-06 8:41 ` dpdklab
2024-03-06 8:42 ` dpdklab
2024-03-06 8:42 ` dpdklab
2024-03-06 8:42 ` dpdklab
2024-03-06 8:42 ` dpdklab
2024-03-06 8:43 ` dpdklab
2024-03-06 8:44 ` dpdklab
2024-03-06 8:48 ` dpdklab
2024-03-06 8:55 ` dpdklab
2024-03-06 8:58 ` dpdklab
2024-03-06 9:03 ` dpdklab
2024-03-06 9:06 ` dpdklab
2024-03-06 9:08 ` dpdklab
2024-03-06 10:02 ` dpdklab
2024-03-06 10:51 ` dpdklab
2024-03-06 10:56 ` dpdklab
2024-03-10 18:02 ` dpdklab
2024-03-10 18:33 ` dpdklab
2024-03-10 19:28 ` dpdklab [this message]
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=65ee09f5.c80a0220.e8a9d.c6a0SMTPIN_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).